From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Sean" Subject: Re: Git-commits mailing list feed. Date: Sat, 23 Apr 2005 14:44:18 -0400 (EDT) Message-ID: <1907.10.10.10.24.1114281858.squirrel@linux1> References: <200504210422.j3L4Mo8L021495@hera.kernel.org> <42674724.90005@ppp0.net> <20050422002922.GB6829@kroah.com> <426A4669.7080500@ppp0.net> <1114266083.3419.40.camel@localhost.localdomain> <426A5BFC.1020507@ppp0.net> <1114266907.3419.43.camel@localhost.localdomain> <20050423175422.GA7100@cip.informatik.uni-erlangen.de> <2911.10.10.10.24.1114279589.squirrel@linux1> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Cc: "Thomas Glanzmann" , "David Woodhouse" , "Jan Dittmer" , "Greg KH" , "Kernel Mailing List" , "Git Mailing List" X-From: git-owner@vger.kernel.org Sat Apr 23 21:39:14 2005 Return-path: Received: from vger.kernel.org ([12.107.209.244]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DPQT2-00011g-8K for gcvg-git@gmane.org; Sat, 23 Apr 2005 21:39:04 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261746AbVDWTnq (ORCPT ); Sat, 23 Apr 2005 15:43:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261738AbVDWTnq (ORCPT ); Sat, 23 Apr 2005 15:43:46 -0400 Received: from simmts8.bellnexxia.net ([206.47.199.166]:20372 "EHLO simmts8-srv.bellnexxia.net") by vger.kernel.org with ESMTP id S261727AbVDWTnk (ORCPT ); Sat, 23 Apr 2005 15:43:40 -0400 Received: from linux1 ([67.71.124.169]) by simmts8-srv.bellnexxia.net (InterMail vM.5.01.06.10 201-253-122-130-110-20040306) with ESMTP id <20050423194340.MAQS1623.simmts8-srv.bellnexxia.net@linux1>; Sat, 23 Apr 2005 15:43:40 -0400 Received: from linux1 (linux1.attic.local [127.0.0.1]) by linux1 (8.12.11/8.12.11) with ESMTP id j3NIiIw6022972; Sat, 23 Apr 2005 14:44:18 -0400 Received: from 10.10.10.24 (SquirrelMail authenticated user sean) by linux1 with HTTP; Sat, 23 Apr 2005 14:44:18 -0400 (EDT) In-Reply-To: To: "Linus Torvalds" User-Agent: SquirrelMail/1.4.4-2 X-Priority: 3 (Normal) Importance: Normal Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org On Sat, April 23, 2005 3:38 pm, Linus Torvalds said: > On Sat, 23 Apr 2005, Sean wrote: >> >> A script that knows how to validate signed tags, can easly strip off all >> the signing overhead for display. Users of scripts that don't >> understand >> will see the cruft, but at least it will still be usable. > > NO. > > Guys, I will say this once more: git will not look at the signature. > > That means that we don't "strip them off", because dammit, they DO NOT > EXIST as far as git is concerned. This is why a tag-file will _always_ > start with > > commit > tag > > because that way we can use fsck and validate reachability and have things > that want trees (or commits) take tag-files instead, and git will > automatically look up the associated tree/commit. And it will do so > _without_ having to understand about signing, since signing is for trust > between _people_ not for git. Yes, totally agreed. > And that is why I from the very beginning tried to make ti very clear > that the signature goes at the end. Not at the beginning, not in the > middle, and not in a different file. IT GOES AT THE END. > Okay now you're just being difficult You're acting like it's impossible for git to grab the SHA1 out of the clear text message if there is signing overhead above the tag reference. That is nonesense. You simply state that tag must include a SHA1 object reference preceded by "REF:" in the comment. Git can surely use this regardless of what signing overhead is above, below or beside it. The suggestion for stripping out the signing overhead was for _human_ readability; git won't care a gnit. Sean