Hi, On Sun, 11 Jan 2009, Andi Kleen wrote: > Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> writes: > > > > For bisect purposes, if you know you're not chasing down a btrfs issue, > > you can do > > > > git bisect good 34353029534a08e41cfb8be647d734b9ce9ebff8 > > Could you perhaps add some standard tag for that commit? That > would make it easier than to always find the exact btrfs commit. > > Just an idea. Well, AFAICT what Linus hinted at is that you do not need such a standard tag. Indeed, you would only clutter the history with such tags, when it usually is just a matter of saying "git bisect good" whenever you _know_ you are hitting known-good history. Ciao, Dscho -- 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
