Re: [RFC/PATCH 3/3] push: add separate 'downstream' branch

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: May 16, 2013, 10:22 UTC
Message-ID: <CAMP44s1eB+bvg7vnG5S3SBACHTrkpCqJNX-Q2tzEVdvzFWvkcA@mail.gmail.com>
In-Reply-To: <CALkWK0m+_AbCd305dU5p5bxwuPPCBKJH7a3e6rHgxxnySMz0pQ@mail.gmail.com>

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

Show 12 quoted lines

> Felipe Contreras wrote:
>>> [remote "origin"]
>>>     push = refs/heads/master:refs/heads/fc/master
>>>
>>> [remote "."]
>>>     push = refs/heads/fc/old-remote/hg:refs/heads/fc/remote/hg
>
> Major thinko.  It should be:
>
> [remote "github"]
>     push = refs/heads/master:refs/heads/fc/master
>     push = refs/heads/fc/old-remote/hg:refs/heads/fc/remote/hg

Would I be able to do:

% git branch --set-upstream-to origin/master --set-downstream-to github/fc/master

Would I see these branches when I do 'git branch -vv'? Would I be able to do 'git push next@{downstream}'?

Show 18 quoted lines

>>> Advantage being you can do:
>>>
>>> [remote "origin"]
>>>     push = refs/heads/*:refs/for/*
>>>
>>> While you can't with branch.<name>.push.
>>
>> But I can do 'git push origin "refs/head/*:refs/heads/for/*"', not
>> that I've ever had the need to do something like that, so I don't
>> care.
>
> Isn't the entire point of this exercise getting git to dwim without
> being explicit?
>
> I don't care about it personally either, which is why I haven't
> written a patch yet.  However, there are users of Gerrit who would
> appreciate this feature: in the remote.pushdefault thread, some people
> requested this feature.

That is orthogonal to 'branch.A.push' the same way 'remote.B.fetch' is orthogonal to 'branch.A.merge'.

-- 
Felipe Contreras