From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: Tags Date: Fri, 01 Jul 2005 09:37:30 -0700 Message-ID: <42C5714A.1020203@zytor.com> References: <42C454B2.6090307@zytor.com> <42C462CD.9010909@zytor.com> <42C46B86.8070006@zytor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Linus Torvalds , Daniel Barkalow , Git Mailing List , Junio C Hamano , ftpadmin@kernel.org X-From: git-owner@vger.kernel.org Fri Jul 01 18:31:32 2005 Return-path: Received: from vger.kernel.org ([12.107.209.244]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DoOPk-00041x-FM for gcvg-git@gmane.org; Fri, 01 Jul 2005 18:30:52 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263388AbVGAQiU (ORCPT ); Fri, 1 Jul 2005 12:38:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263387AbVGAQiU (ORCPT ); Fri, 1 Jul 2005 12:38:20 -0400 Received: from terminus.zytor.com ([209.128.68.124]:970 "EHLO terminus.zytor.com") by vger.kernel.org with ESMTP id S263378AbVGAQiG (ORCPT ); Fri, 1 Jul 2005 12:38:06 -0400 Received: from [172.27.0.18] (c-67-180-239-42.hsd1.ca.comcast.net [67.180.239.42]) (authenticated bits=0) by terminus.zytor.com (8.13.1/8.13.1) with ESMTP id j61GbV14022966 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Jul 2005 09:37:32 -0700 User-Agent: Mozilla Thunderbird 1.0.2-1.3.3 (X11/20050513) X-Accept-Language: en-us, en To: "Eric W. Biederman" In-Reply-To: X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on localhost X-Virus-Status: Clean X-Spam-Status: No, score=-0.9 required=5.0 tests=AWL,BAYES_00, RCVD_IN_SORBS_DUL autolearn=no version=3.0.3 X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on terminus.zytor.com Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Eric W. Biederman wrote: > "H. Peter Anvin" 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 :) > > Still being a complete git dummy I think the trivial mapping is > to put tags in: > .git/refs/tags/user@domain/tag > and then have a symlink at: > .git/TAGS > that points to your default directory of tags. > Unless you have an authentication mechanism and *enforce* it (you can do that with GPG signatures if *and only if* your disambiguation includes your GPG signature fingerprint) you still have a problem with someone introducing fake tags as a DoS attack. -hpa