On Tue, 24 Jun 2008, Junio C Hamano wrote: > Instead of having a set of bisect/good-* refs and a single bisect-bad ref, > your "fixed and unfixed" mode could work quite differently. By noticing > that the topology the user specified with initial good and bad have > ancient bad and recent good --- that is, "it used to be bad but now it is > good" --- you could instead use a set of bisect/bad-* refs and a single > bisect-good ref, and feed good and bad swapped to "rev-list --bisect" in > bisect_next(). That way, the labels given by visualize will match what > the user is doing automatically. ... and the final answer would be "the first good commit is ...". That would be awesome, much nicer than yet more keywords. > I said "it makes sense in its own way", because it is _quite_ different > from how git-bisect currently assumes, and restructuring git-bisect to > operate naturally in a way Michael describes would be a much larger > surgery with costs (including risks of bugs) associated with it, which > needs to be weighed in when judging that approach would actually make > sense. > -- > 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 > Nicolas -- 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
