On Sunday 03 June 2007, Pierre Habouzit wrote: > On Sun, Jun 03, 2007 at 08:59:18AM -0400, Michael Poole wrote: > > Pierre Habouzit writes: > > > > > The other problem I see is that at the time a bug gets reported, the > > > user knows it's found at a commit say 'X'. But it could in fact have > > > been generated at a commit Y, with this pattern: > > > > > > --o---o---Y---o---o---o---o---X---o---o--> master > > > \ > > > o---o---o---o---o---o--> branch B > > > > Mainly for that reason, I would suggest having it outside the code > > base's namespace: probably a different root in the same $GIT_DIR, but > > I can see people wanting to have a separate $GIT_DIR. If the database > > tracks bugs by what commit(s) introduce or expose the bug -- at least > > once that is known -- then you get nearly free tracking of which > > branches have the bug without having to check out largely redundant > > trees. > > Sure, but if it's completely out-of-tree, then cloning a repository > don't allow you to get the bug databases with it for free. I mean it'd > be great to have it somehow linked to the repository, but also I agree > that not everybody wants to clone the whole bugs databases. So maybe it > should just be in another shadow branch that annotates the devel ones. > Hmmm I definitely need to read the git-note thread... I guess I'm the one responsible for starting that git-note thread... For the moment, I'm busy implementing some concepts that came out of that discussion (refactoring tag objects and building some infrastructure needed to support notes without the drawbacks present in my first version). Hopefully I'll have a proof-of-concept ready before too long. In the meantime I'll be happy to answer questions you might have. Regarding the notes themselves, I thought about possibly using them as a link between the repo and the bug tracker, with some glue code in between for making the connections. I haven't thought about integrating them more deeply into a bug tracker, but it might be worth thinking along those lines, especially for the kind of system you're proposing. Now, back to hacking... Have fun! :) ...Johan -- Johan Herland, <johan@xxxxxxxxxxx> www.herland.net - 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
