Petr Baudis wrote: > Dear diary, on Fri, Jul 01, 2005 at 03:56:06PM CEST, I got a letter > where "Eric W. Biederman" <ebiederm@xmission.com> told me that... > >>"H. Peter Anvin" <hpa@zytor.com> writes: >> >> >>>In the end, it might be that the right thing to do for git on kernel.org is to >>>have a single, unified object store which isn't accessible by anything other >>>than git-specific protocols. There would have to be some way of dealing with, >>>for example, conflicting tags that apply to different repositories, though. >> >>As far as I can tell public distributed tags are not that hard and if >>you are going to be synching them it is probably worth working on. >> >>The basic idea is that instead of having one global tag of >>'linux-2.6.13-rc1' you have a global tag of >>'torvalds@osdl.org/linux-2.6.13-rc1'. >> >>The important part is that the tag namespace is made hierarchical >>with at least 2 levels. Where the top level is a globally >>unique tag owner id and the bottom level is the actual tag. This >>prevents collisions when merging trees because two peoples >>tags are never in the same namespace, as least when >>people are not actively hostile :) > > > I don't know, I don't consider this very appealing myself. I'd rather > prefer the private tags to be per-repository rather than per-user, since > those ugly "merged-here", "broken" etc. tags aren't very useful on > larger scope than of a repository. OTOH, what tags would be per-user, > not per-repository and not global? > He's talking about global tags, just using a "globally unique" namespace. Which of course only works right if only genuinely can't create tags outside your assigned namespace. -hpa - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Sat Jul 02 04:41:34 2005
This archive was generated by hypermail 2.1.8 : 2005-07-02 04:41:35 EST