On Mon, 23 Jun 2008, Ingo Molnar wrote: > tags are mostly meant for release management - our use of tags to save > the "merge base" of topic branches in -tip can be considered mild abuse. > > ( But we did not want to pullute the already crowded branch space with > extra technical branches. -tip has 127 branches at this moment, 89 of > which are topic branches - creating a base branch for each topic would > add another 89 branches and bring it all up to 216 branches. ) If these are only internal details, and not something you expect other people to use, you could get yourself a directory for refs that doesn't mean anything to the rest of git. If you use "refs/bases/<something>", git should (a) accept that as a name you can use for a commit; (b) preserve anything referenced by it; (c) copy it in a "git clone --mirror"; and pretty much ignore it otherwise. -Daniel *This .sig left intentionally blank* -- 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
