Back Midas Rome Roody Rootana
  Midas DAQ System  Not logged in ELOG logo
Entry  13 Feb 2013, Konstantin Olchanski, Info, Review of github and bitbucket 
    Reply  14 Feb 2013, Stefan Ritt, Info, Review of github and bitbucket 
       Reply  01 Apr 2013, Randolf Pohl, Info, Review of github and bitbucket 
          Reply  02 Apr 2013, Konstantin Olchanski, Info, Review of github and bitbucket 
             Reply  02 Apr 2013, Randolf Pohl, Info, Review of github and bitbucket 
          Reply  03 Apr 2013, Stefan Ritt, Info, Review of github and bitbucket 
             Reply  03 Apr 2013, Randolf Pohl, Info, Review of github and bitbucket 
Message ID: 871     Entry time: 03 Apr 2013     In reply to: 870
Author: Randolf Pohl 
Topic: Info 
Subject: Review of github and bitbucket 
> > * "git bisect" for finding which commit introduced a (reproducible) bug.
> 
> I did not know this command, so I read about it. This IS WONDERFUL! I had once (actually with MSCB) the case that a bug was introduced i the last 100 
> revisions, but I did not know in which. So I checked out -1, -2, -3 revisions, then thought a bit, then tried -99, -98, then had the bright idea to try -50, then 
> slowly converged. Later I realised that I should have done a binary search, like -50, if ok try -25, if bad try -37, and so on to iteratively find the offending 
> commit. Finding that there is a command it git which does this automatically is great news.

even more so considering the nonlinear history (due to branching) in a regular git repo.
ELOG V3.1.4-2e1708b5