[PATCH 6/6] remote.c: introduce branch.name.pushremote

2013-04-02 Thread Ramkumar Ramachandra
This new configuration variable overrides `remote.pushdefault` and `branch.name.remote` for pushes. When you pull from one place (e.g. your upstream) and push to another place (e.g. your own publishing repository), you would want to set `remote.pushdefault` to specify the remote to push to for

[PATCH 6/6] remote.c: introduce branch.name.pushremote

2013-03-28 Thread Ramkumar Ramachandra
This new configuration variable overrides `remote.pushdefault` and `branch.name.remote` for pushes. When you pull from one place (e.g. your upstream) and push to another place (e.g. your own publishing repository), you would want to set `remote.pushdefault` to specify the remote to push to for

Re: [PATCH 6/6] remote.c: introduce branch.name.pushremote

2013-03-22 Thread Junio C Hamano
Ramkumar Ramachandra artag...@gmail.com writes: This new configuration variable overrides `remote.pushdefault` and `branch.name.remote` for pushes. In a typical triangular-workflow setup, you would want to set `remote.pushdefault` to specify the remote to push to for all branches, and use

Re: [PATCH 6/6] remote.c: introduce branch.name.pushremote

2013-03-20 Thread Tay Ray Chuan
On Wed, Mar 20, 2013 at 8:45 PM, Ramkumar Ramachandra artag...@gmail.com wrote: This new configuration variable overrides `remote.pushdefault` and `branch.name.remote` for pushes. In a typical triangular-workflow setup, you would want to set `remote.pushdefault` to specify the remote to push

Re: [PATCH 6/6] remote.c: introduce branch.name.pushremote

2013-03-20 Thread Ramkumar Ramachandra
Tay Ray Chuan wrote: On Wed, Mar 20, 2013 at 8:45 PM, Ramkumar Ramachandra artag...@gmail.com wrote: This new configuration variable overrides `remote.pushdefault` and `branch.name.remote` for pushes. In a typical triangular-workflow setup, you would want to set `remote.pushdefault` to