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

From: Ramkumar Ramachandra <artagnon@gmail.com>
Date: May 16, 2013, 09:20 UTC
Message-ID: <CALkWK0nOywB5BtHnKZQ_+wsJNp82zk7-YJw_S15quqH+iU=jWg@mail.gmail.com>
In-Reply-To: <CAMP44s3fPsGW_9aBbcsu8cJAagz8JEWV2HM=XRH3Rw4=SXdL7Q@mail.gmail.com>

Felipe Contreras wrote:

> And is going to change soon.

Your point being?  How will this patch interact with push.default = matching?

Show 5 quoted lines

>> branch.<name>.push should probably be named
>> branch.<name>.downstreamref and be used only for informational
>> purposes (@{d} and git status)?
>
> That makes absolutely no sense.

I said downstreamref, not downstreamrefspec.

Show 13 quoted lines

> [branch "master"]
>           remote = origin
>           merge = refs/heads/master
>           pushremote = github
>           push = refs/heads/fc/master
>
> [branch "fc/old-remote/hg"]
>           remote = .
>           merge = refs/heads/master
>           pushremote = github
>           push = refs/heads/fc/remote/hg
>
> Tell me how you express that without 'remote.branch.push'.

[remote "origin"]
    push = refs/heads/master:refs/heads/fc/master

[remote "."]
    push = refs/heads/fc/old-remote/hg:refs/heads/fc/remote/hg

Advantage being you can do:

[remote "origin"]
    push = refs/heads/*:refs/for/*

While you can't with branch.<name>.push.