[PATCH v2 0/6] Support triangular workflows · Ramkumar Ramachandra <hidden> · 2016-06-15
[PATCH 2/6] t5516 (fetch-push): update test description · Ramkumar Ramachandra <hidden> · 2016-06-15
Re: [PATCH 2/6] t5516 (fetch-push): update test description · Jonathan Nieder <hidden> · 2016-06-15
Re: [PATCH 2/6] t5516 (fetch-push): update test description · Ramkumar Ramachandra <hidden> · 2016-06-15
Re: [PATCH 2/6] t5516 (fetch-push): update test description · Jonathan Nieder <hidden> · 2016-06-15
[PATCH 1/6] remote.c: simplify a bit of code using git_config_string() · Ramkumar Ramachandra <hidden> · 2016-06-15
Re: [PATCH 1/6] remote.c: simplify a bit of code using git_config_string() · Jonathan Nieder <hidden> · 2016-06-15
Re: [PATCH 1/6] remote.c: simplify a bit of code using git_config_string() · Ramkumar Ramachandra <hidden> · 2016-06-15
[PATCH 4/6] remote.c: introduce a way to have different remotes for fetch/push · Ramkumar Ramachandra <hidden> · 2016-06-15
Re: [PATCH 4/6] remote.c: introduce a way to have different remotes for fetch/push · Jonathan Nieder <hidden> · 2016-06-15
[PATCH 3/6] t5516 (fetch-push): introduce mk_test_with_name() · Ramkumar Ramachandra <hidden> · 2016-06-15
Re: [PATCH 3/6] t5516 (fetch-push): introduce mk_test_with_name() · Jonathan Nieder <hidden> · 2016-06-15
Re: [PATCH 3/6] t5516 (fetch-push): introduce mk_test_with_name() · Ramkumar Ramachandra <hidden> · 2016-06-15
Re: [PATCH 3/6] t5516 (fetch-push): introduce mk_test_with_name() · Jonathan Nieder <hidden> · 2016-06-15
Re: [PATCH 3/6] t5516 (fetch-push): introduce mk_test_with_name() · Jeff King <hidden> · 2016-06-15
Re: [PATCH 3/6] t5516 (fetch-push): introduce mk_test_with_name() · Jonathan Nieder <hidden> · 2016-06-15
[PATCH 6/6] remote.c: introduce branch.<name>.pushremote · Ramkumar Ramachandra <hidden> · 2016-06-15
Re: [PATCH 6/6] remote.c: introduce branch.<name>.pushremote · Tay Ray Chuan <hidden> · 2016-06-15
Re: [PATCH 6/6] remote.c: introduce branch.<name>.pushremote · Ramkumar Ramachandra <hidden> · 2016-06-15
[PATCH 5/6] remote.c: introduce remote.pushdefault · Ramkumar Ramachandra <hidden> · 2016-06-15
Re: [PATCH 5/6] remote.c: introduce remote.pushdefault · Jonathan Nieder <hidden> · 2016-06-15
Re: [PATCH 5/6] remote.c: introduce remote.pushdefault · Ramkumar Ramachandra <hidden> · 2016-06-15
Re: [PATCH v2 0/6] Support triangular workflows · Tay Ray Chuan <hidden> · 2016-06-15
Re: [PATCH v2 0/6] Support triangular workflows · Ramkumar Ramachandra <hidden> · 2016-06-15
Re: [PATCH v2 0/6] Support triangular workflows · Philip Oakley <hidden> · 2016-06-15
Re: [PATCH v2 0/6] Support triangular workflows · Ramkumar Ramachandra <hidden> · 2016-06-15

Re: [PATCH v2 0/6] Support triangular workflows

From: Ramkumar Ramachandra <hidden>
Date: 2016-06-15 22:56:28

Tay Ray Chuan wrote:

On Wed, Mar 20, 2013 at 8:44 PM, Ramkumar Ramachandra
[off-list ref] wrote:

quoted

  remote.c: introduce remote.pushdefault
  remote.c: introduce branch.<name>.pushremote

Perhaps we should clarify how this differs from remote.pushurl in the
documentation for it, in git-config and/or git-push. Maybe even
include the design decisions behind it from [1]. :)

http://thread.gmane.org/gmane.comp.version-control.git/215702/focus=215717

Actually, it's quite obvious when you think about it: remote.pushurl
doesn't allow remote tracking branches, and this is a very serious
limitation.  If anything, the documentation for remote.pushurl should
be updated to explain that it has a very narrow usecase (will do in a
future patch).

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help