René Scharfe wrote: > Am 03.06.2012 09:11, schrieb Jim Meyering: >> Perhaps a more palatable change, here and in the other two places: >> s/seeked/cg-seek'd/, i.e., >> >> - * "git bisect" showed mysterious "won't bisect on seeked tree" error message. >> + * "git bisect" showed mysterious "won't bisect on cg-seek'd tree" >> error message. >> >> Then, if someone does this again, it will be more obvious that >> it is not a typo. > > This change is only valid if the command "git bisect" at some point > printed "won't bisect on cg-seek'd tree" instead of "won't bisect on > seeked tree". And even then, it doesn't make now sense to change > already published release notes (Documentation/RelNotes/1.5.4.4.txt), > after the fact. You're right. Changing the RelNotes that way would not be useful. However, changing git-bisect.sh should make it easier for non-native English speakers to understand that obscure diagnostic. -- 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