[PATCH 5/6] remote.c: introduce remote.pushdefault

2013-04-02 Thread Ramkumar Ramachandra
This new configuration variable defines the default remote to push to, and overrides `branch.name.remote` for all branches. It is useful in the typical triangular-workflow setup, where the remote you're fetching from is different from the remote you're pushing to. Signed-off-by: Ramkumar

[PATCH 5/6] remote.c: introduce remote.pushdefault

2013-03-28 Thread Ramkumar Ramachandra
This new configuration variable defines the default remote to push to, and overrides `branch.name.remote` for all branches. It is useful in the typical triangular-workflow setup, where the remote you're fetching from is different from the remote you're pushing to. Signed-off-by: Ramkumar

Re: [PATCH 5/6] remote.c: introduce remote.pushdefault

2013-03-27 Thread Ramkumar Ramachandra
Jeff King wrote: but also possibly just move it with the other remote parsing, like: [...] Done. Thanks for the dose of sanity. -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at

[PATCH 5/6] remote.c: introduce remote.pushdefault

2013-03-22 Thread Ramkumar Ramachandra
This new configuration variable defines the default remote to push to, and overrides `branch.name.remote` for all branches. It is useful in the typical triangular-workflow setup, where the remote you're fetching from is different from the remote you're pushing to. Signed-off-by: Ramkumar

Re: [PATCH 5/6] remote.c: introduce remote.pushdefault

2013-03-22 Thread Jeff King
On Fri, Mar 22, 2013 at 01:22:35PM +0530, Ramkumar Ramachandra wrote: diff --git a/remote.c b/remote.c index 185ac11..bdb542c 100644 --- a/remote.c +++ b/remote.c @@ -350,6 +350,11 @@ static int handle_config(const char *key, const char *value, void *cb) const char *subkey;

[PATCH 5/6] remote.c: introduce remote.pushdefault

2013-03-20 Thread Ramkumar Ramachandra
This new configuration variable defines the default remote to push to, and overrides `branch.name.remote` for all branches. It is useful in the typical triangular-workflow setup, where the remote you're fetching from is different from the remote you're pushing to. Signed-off-by: Ramkumar

Re: [PATCH 5/6] remote.c: introduce remote.pushdefault

2013-03-20 Thread Jonathan Nieder
Ramkumar Ramachandra wrote: This new configuration variable defines the default remote to push to, and overrides `branch.name.remote` for all branches. Micronit: I think this would be easier to explain if it came after patch 6, since then you could say In other words, it is a default for

Re: [PATCH 5/6] remote.c: introduce remote.pushdefault

2013-03-20 Thread Junio C Hamano
Jonathan Nieder jrnie...@gmail.com writes: Ramkumar Ramachandra wrote: This new configuration variable defines the default remote to push to, and overrides `branch.name.remote` for all branches. Micronit: I think this would be easier to explain if it came after patch 6, since then you

Re: [PATCH 5/6] remote.c: introduce remote.pushdefault

2013-03-20 Thread Ramkumar Ramachandra
Jonathan Nieder wrote: Ramkumar Ramachandra wrote: This new configuration variable defines the default remote to push to, and overrides `branch.name.remote` for all branches. Micronit: I think this would be easier to explain if it came after patch 6, since then you could say In other words,