Re: [3/4] What's not in 1.5.2 (new topics)

From: Petr Baudis <pasky@suse.cz>
Date: May 18, 2007, 12:41 UTC
Message-ID: <20070518124123.GX4489@pasky.or.cz>
In-Reply-To: <f2k4g6$879$2@sea.gmane.org>

On Fri, May 18, 2007 at 02:00:07PM CEST, Jakub Narebski wrote:

Show 8 quoted lines

> There is a bit ugly solution for this: instead of using symbolic name
> in versioned .gitmodules for a subproject (for a repo), use subproject
> identifier (inode), and put it in the tag object (or config) together with
> the URL.  Git would then search all the subproject / submodule info for
> a given inode.  You could have more than one inode / identifier name for
> a subproject repo; this would avoid the "independently created" issue
> with using inodes / file-ids in distributed SCM.  One would have to
> ensure however that different subprojects get assigned different inodes.

Well, then it doesn't make any difference, no? You just renamed the problem but it stays the same - to ensure uniqueness even across repositories.

Ok, you can declare now that you will just think out a UUID for the subproject, but aside of not fitting well with the whole git philosophy, then you don't need the indirection again, just use the UUID as the tag name.

I have the feeling that I'm missing something basic in your proposal...

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Ever try. Ever fail. No matter. // Try again. Fail again. Fail better.
		-- Samuel Beckett