From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Sixt Subject: Re: [3/4] What's not in 1.5.2 (new topics) Date: Fri, 18 May 2007 12:16:26 +0200 Organization: eudaptics software gmbh Message-ID: <464D7CFA.B983778B@eudaptics.com> References: <200705170539.11402.andyparkins@gmail.com> <200705180857.18182.andyparkins@gmail.com> <20070518085708.GC4708@mellanox.co.il> <200705181040.37648.andyparkins@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: git@vger.kernel.org X-From: git-owner@vger.kernel.org Fri May 18 12:16:52 2007 Return-path: Envelope-to: gcvg-git@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1HozVz-0004kP-Ls for gcvg-git@gmane.org; Fri, 18 May 2007 12:16:52 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754788AbXERKQT (ORCPT ); Fri, 18 May 2007 06:16:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754633AbXERKQT (ORCPT ); Fri, 18 May 2007 06:16:19 -0400 Received: from main.gmane.org ([80.91.229.2]:36253 "EHLO ciao.gmane.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754788AbXERKQS (ORCPT ); Fri, 18 May 2007 06:16:18 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HozVC-0001KT-0J for git@vger.kernel.org; Fri, 18 May 2007 12:16:02 +0200 Received: from cm56-163-160.liwest.at ([86.56.163.160]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 18 May 2007 12:16:01 +0200 Received: from J.Sixt by cm56-163-160.liwest.at with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 18 May 2007 12:16:01 +0200 X-Injected-Via-Gmane: http://gmane.org/ X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: cm56-163-160.liwest.at X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: Andy Parkins wrote: > On Friday 2007 May 18, Michael S. Tsirkin wrote: > > I wouldn't be happy: I have just cloned both project and superproject, > > but to re-publish the superproject using my clone of subproject, I have > > to create a new commit, which would have a different hash from the origin. > > So how do people know they can trust my tree? > > That problem exists regardless of the method of changing URL - in your method > though the change is entirely unrecorded because you've changed something > that upstream supplied in an out-of-band manner. And it doesn't matter: Once you trust the superproject with its .gitmodules (versioned or not), the trust is based on the SHA1 of the gitlink entry. Where the so named subproject commit came from is secondary. -- Hannes