Pierre Habouzit <madcoder@xxxxxxxxxx> writes: > Yeah, now that I read that thread, well yeah, I think notes are a hell > of a good concept for my ideas. I mean, a bug report would be basically > a collection of notes: > * the bug has been found at this commit ; > * the bug has been not-found at this commit ; > * this commit is a fix for that bug ; That's my feeling too. "Commiting" bug information in the tree is only half of a good idea. You want to be able to say, after the fact, "This commit had bug XYZ". OTOH, the idea (followed by bugs everywhere) that merging a branch would automatically close bugs fixed by this branch is a really cool thing. The kind of information you're mentionning above can be a great starting point for "bisect". I can even imagine a kind of distributed bisect, where several users could give their "bad commits" for the same bug. -- Matthieu - 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
