Using git to track down the commit that caused a bug

Bron Gondwana brong at fastmail.fm
Wed Feb 4 04:15:29 EST 2009


On Mon, Feb 02, 2009 at 01:21:05PM +1100, Bron Gondwana wrote:
> I've rebuilt my github clones from direct copies of the Cyrus CVS
> repository at CMU.  Now that I have a local account at CMU I've
> been able to do a CVS import in such a way that it can follow CVS
> as changes get committed, which is much nicer.

Speaking of which (man, I love working with git)

root at brongtest1:/usr/src/cyrus# git bisect log
# bad: [038f3234a5f2aa7743de4e95faccc5cfaea79b1b] ME stuff
# good: [8f55805337283f22a422434ae937ca020150b5c9] dodge the
# destructively edited nbuf by moving the logging & update notify to
# before the mailbox_close
# http://bugzilla.andrew.cmu.edu/show_bug.cgi?id=3071
git-bisect start 'fastmail' '8f55805337283f22a422434ae937ca020150b5c9'
# bad: [dbcde9bb036950658aff123c7cfe00ae535db21a] Explicit uquota_t on
# all quota additions
git-bisect bad dbcde9bb036950658aff123c7cfe00ae535db21a
# bad: [17bb4fd1722da9a3c3287ed5cf35e6c9e800e16c] fix a potential memory
# corruption (thanks to Bron Gondwana)
git-bisect bad 17bb4fd1722da9a3c3287ed5cf35e6c9e800e16c
# good: [67c817e9e79f83b6cd5743ecea00a66c99817783] don't create a tls
# session DB during purge if it doesn't already exist
git-bisect good 67c817e9e79f83b6cd5743ecea00a66c99817783
# good: [5bdb3eeb15d224a384678a593230a488a7ad34d3] only include message
# files mentioned in the index in the quota calculation
git-bisect good 5bdb3eeb15d224a384678a593230a488a7ad34d3
# bad: [0f8f2b053b7a4bbd843bec9a52b007179d77c356] Fixed incompatibility
# between older ManageSieve clients and newer   servers that issue an
# auto-capability response after AUTH with a   SASL security layer
git-bisect bad 0f8f2b053b7a4bbd843bec9a52b007179d77c356
# good: [ddac2bdd945974bb2bc06a5f6944d701a621a2b0] move APOP challenge
# back to end of banner so we don't end up with an extra space after +OK
# if we don't have an APOP challenge
git-bisect good ddac2bdd945974bb2bc06a5f6944d701a621a2b0

0f8f2b053b7a4bbd843bec9a52b007179d77c356 is first bad commit
commit 0f8f2b053b7a4bbd843bec9a52b007179d77c356
Author: murch <murch>
Date:   Wed Jan 14 15:50:47 2009 +0000

    Fixed incompatibility between older ManageSieve clients and newer
      servers that issue an auto-capability response after AUTH with a
      SASL security layer



More information about the Info-cyrus mailing list