On lundi 25 janvier 2010, John Koleszar wrote: > On Wed, 2010-01-20 at 21:05 -0500, Johan Herland wrote: > > On Wednesday 20 January 2010, Joey Hess wrote: > > > 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. Perhaps you can read about "git replace" in my article: http://www.kernel.org/pub/software/scm/git/docs/git-bisect-lk2009.html and/or my related presentation: http://www.linux-kongress.org/2009/slides/fighting_regressions_with_git_bisect_christian_couder.pdf I think in the long run it's much better to use git replace rather than notes, especially as replace refs for bisecting could be in their own refs/replace/bisect namespace. I may take the time to implement that soon if you or other people are interested. Regards, Christian. -- 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