Re: [RFD] making separate-remote layout easier to use

From: Junio C Hamano <junkio@cox.net>
Date: Nov 25, 2006, 23:19 UTC
Message-ID: <7vvel3yuzz.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <ekafpm$fs7$1@sea.gmane.org>

Jakub Narebski <jnareb@gmail.com> writes:

Show 13 quoted lines

> Junio C Hamano wrote:
>
>> Now separate-remote layout is the default for newly cloned
>> repositories, I think it is a good time to make further effort
>> to make things easier to use.  Here are some of the ideas off
>> the top of my head.
> [...]
>> * Change the default contents of $GIT_DIR/remotes/origin
>
> The question is: do we continue to use remotes/ file, or do we
> save remotes info in the config file: remote.<name>.url,
> remote.<name>.fetch, remote.<name>.push and branch.<name>.merge
> (in our case '[remote "origin"]' section)?

It is not "the question"; it is irrelevant because $GIT_DIR/remotes/origin and [remote "origin"] are pretty much interchangeable, and will hopefully continue to be.

        [remote "origin"]
                url = master.kernel.org:/pub/scm/git/git.git/
                fetch = +refs/heads/master:refs/remotes/origin/master
                fetch = +refs/heads/*:refs/remotes/origin/*

would be the way to express the equilvalent of the example in the previous message.