On Wed, 2010-01-20 at 21:05 -0500, Johan Herland wrote: > On Wednesday 20 January 2010, Joey Hess wrote: > > Johan Herland wrote: > > > > PS, Has anyone thought about using notes to warn bisect away from > > > > commits that are known to be unbuildable or otherwise cause bisection > > > > trouble? > > > > > > No, I haven't thought of that specific use case. Great idea! :) > > [...] > > In any case, I would not use "git notes" to maintain the bisect hints. > Rather, I'd add subcommands to "git bisect" that would take care of > maintaining the notes tree @ "refs/notes/bisect". Much more user-friendly > than telling the user to write their own bisect-notes by hand. > I haven't read up on notes more than enough to know its in the pipe, but I had a similar idea for using them to store bisect hints. I've been doing a lot of bisecting lately into a range that had a couple dormant bugs where I'm trying to bisect bug B but bug A prevents me from making a determination. Rather than skip what I know is an interesting commit, I cherry-pick the bugfix commit(s) A' and test that, then reset and continue bisecting. Teaching bisect to consistently skip a commit, or to automatically squash in A' if we have A and not A', would be a desirable feature. I will have to read up some more on notes. -- 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