Re: [PATCH 1/3] fetch: add --allow-local option

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: May 16, 2013, 12:54 UTC
Message-ID: <CAMP44s2Wf7ZfmQ-7UGy2fNRX3TXaRMDu3WtZzz-WEOHibRAWVA@mail.gmail.com>
In-Reply-To: <CALkWK0m=-ePHCLChrBSgD_cUk=MOSt15aYf-yXhn_LpDro88fw@mail.gmail.com>

On Thu, May 16, 2013 at 5:32 AM, Ramkumar Ramachandra <artagnon@gmail.com> wrote:

Show 7 quoted lines

> Felipe Contreras wrote:
>> Answer: because 'git fetch .' doesn't make any sense. So if
>> 'branch.HEAD.remote' is '.' it doesn't make sense to do 'git fetch .'.
>
> I agree that 'git fetch .' is currently not useful (and I am not
> against changing its behavior), but my question pertains to why you
> are replacing it with the hard-coded "origin".

'origin' is already hard-coded.

% git clone git://git.kernel.org/pub/scm/git/git.git

What would be the name of the remote? 'origin'.

% git checkout --no-track -b test % git fetch

What is the remote that is used? 'origin'.

> What happens when I
> git branch -t -b devel hot-branch where branch.hot-branch.remote = ram
> and not origin?

The same thing that happens when you git branch --no-track -b devel hot-branch.

-- 
Felipe Contreras