Re: [PATCH 07/16] git-read-tree: take --submodules option

From: Junio C Hamano <junkio@cox.net>
Date: May 24, 2007, 20:59 UTC
Message-ID: <7vps4quecz.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20070524205535.GP4489@pasky.or.cz>

Petr Baudis <pasky@suse.cz> writes:

Show 10 quoted lines

> On Thu, May 24, 2007 at 10:32:32PM CEST, Junio C Hamano wrote:
> ...
>> It's just bare/pure layout is easier to understand because it is
>> essentially a "mirror" of the upstream.
>
> I OTOH think that it's less confusing to just keep it the same for all
> the normal repositories - and you yourself did not rule out the
> possibility to have local changes in the repository, in which case we
> certainly should use the separate-remotes layout or we go back to last
> year's refs mess.

That "local changes in the repository" will happen in the clone created in kernel-src/ directory and I do not have any problem using separate remotes there. I was talking about the refs layout used in .git/subproject/kernel26/, which is a mirror of the upstream and the clone source for that (temporarily checked out) repository at kernel-src/ directory. After all, the "mirror" is where you would push your local changes back into, and it is more common to use non-separate-remote layout (without even 'master'->'origin' mapping, hence I had to come up with a new name 'pure', but I realize that what I meant really is a 'mirror') there.