Trevor Saunders <tbsaunde@xxxxxxxxxxxx> writes: > When the first bad commit has been found git bisect prints something > like this: > > <40 char sha1> is the first bad commit > Commit <40 char sha1> > ... > > :100644 100644 10f5e57... a46cfeb... M bisect.c > :100755 100755 ae3fec2... 65a19fa... M git-bisect.sh > > The raw diff output is not really useful, and its kind of silly to print > the sha1 twice. Instead lets print something like this: > > The first bad commit is > Commit <sha1> > ... According to +CCouder, this change will break existing people's use cases. See $gmane/268881 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html