From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [git patches] libata updates, GPG signed (but see admin notes) Date: Mon, 31 Oct 2011 15:20:48 -0700 Message-ID: <4EAF1F40.3030907@zytor.com> References: <20111026202235.GA20928@havoc.gtf.org> <1319969101.5215.20.camel@dabdike> <1320049150.8283.19.camel@dabdike> <7vy5w1ow90.fsf@alter.siamese.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Junio C Hamano , git@vger.kernel.org, James Bottomley , Jeff Garzik , Andrew Morton , linux-ide@vger.kernel.org, LKML To: Linus Torvalds X-From: linux-ide-owner@vger.kernel.org Mon Oct 31 23:21:07 2011 Return-path: Envelope-to: lnx-linux-ide@lo.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RL0E5-0000cQ-Qg for lnx-linux-ide@lo.gmane.org; Mon, 31 Oct 2011 23:21:06 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934176Ab1JaWVE (ORCPT ); Mon, 31 Oct 2011 18:21:04 -0400 Received: from terminus.zytor.com ([198.137.202.10]:40592 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934139Ab1JaWVD (ORCPT ); Mon, 31 Oct 2011 18:21:03 -0400 Received: from anacreon.sc.intel.com (jfdmzpr03-ext.jf.intel.com [134.134.139.72]) (authenticated bits=0) by mail.zytor.com (8.14.5/8.14.5) with ESMTP id p9VMKrXG004370 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 31 Oct 2011 15:20:54 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20110927 Thunderbird/7.0 In-Reply-To: X-Enigmail-Version: 1.3.2 Sender: linux-ide-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ide@vger.kernel.org Archived-At: On 10/31/2011 03:18 PM, Linus Torvalds wrote: > On Mon, Oct 31, 2011 at 11:23 AM, Junio C Hamano wrote: >> >> It certainly lets you run "git tag --verify" after you pulled and will >> give you assurance that you pulled the right thing from the right person, >> but what do you plan to do to the tag from your lieutenants after you >> fetched and verified? I count 379 merges by you between 3.0 (2011-07-21) >> and 3.1 (2011-10-24), which would mean you would see 4-5 tags per day on >> average. Will these tags be pushed out to your public history? > > No, you misunderstand. > > I can do that kind of "crazy manual check of a tag" today. And it's > too painful to be useful in the long run (or even the short run - I'd > much prefer the pgp signature in the email which is easier to check > and more visible anyway). Fetching a tag by name and saving it as a > tag is indeed pointless. > > But what would be nice is that "git pull" would fetch the tag (based > on name) *automatically*, and not actually create a tag in my > repository at all. Instead, if would use the tag to check the > signature, and - if we do this right - also use the tag contents to > populate the merge commit message. > > In other words, no actual tag would ever be left around as a turd, it > would simply be used as an automatic communication channel between the > "git push -s" of the submitter and my subsequent "git pull". Neither > side would have to do anything special, and the tag would never show > up in any relevant tree (it could even be in a totally separate > namespace like "refs/pullmarker/" or something). > Perhaps we should introduce the notion of a "private tag" or something along those lines? (I guess that would still have to be possible to push it, but not pull it by default...) -hpa