git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 0/4] Support triangular workflows

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Mar 18, 2013, 13:16 UTC
Message-ID
<1363612575-7340-1-git-send-email-artagnon@gmail.com>
Hi,

This series follows up a previous discussion with Junio and Jeff [1]. It attempts to support the triangular workflow, where the remote you're fetching from is not the same as the remote you're pushing to. `remote.<name>.pushurl` has already been discussed, and deemed as a poor solution to the problem [2].

[1/4] is a minor cleanup patch to make other patches consistent with the existing style.

[2/4] introduces the infrastructure needed to allow [3/4] and [4/4] to be simple configuration-adding patches.

[3/4] and [4/4] add the proposed configuration options. They're very simple patches, but the documentation is not so simple: I've documented all the side-effects of the other configuration option in each configuration option, to give the reader a comprehensive picture when reading one configuration option.

I've put off implementing remote.default corresponding to remote.pushdefault, as Jeff suggested in [1], because it's currently not an itch; apart from the obvious symmetry, I don't know what purpose it serves: why would anyone want to fetch from a remote other than origin by default? Why wouldn't they simply swap that remote's name with "origin"? However, it's a nice thing to have for symmetry, and it should be trivial to implement: any interested person is welcome to pick it up.

The series works as expected, and all tests pass.
Thanks for reading.

[1]: http://thread.gmane.org/gmane.comp.version-control.git/215763 [2]: http://thread.gmane.org/gmane.comp.version-control.git/215702/focus=215717

Ramkumar Ramachandra (4):
  remote.c: simply a bit of code using git_config_string()
  remote.c: introduce a way to have different remotes for fetch/ push
  remote.c: introduce remote.pushdefault
  remote.c: introduce branch.<name>.pushremote
 Documentation/config.txt | 23 ++++++++++++++++---
 builtin/push.c           |  2 +-
 remote.c                 | 60 +++++++++++++++++++++++++++++++++++-------------
 remote.h                 |  1 +
 4 files changed, 66 insertions(+), 20 deletions(-)
-- 
1.8.2
Next: Ramkumar Ramachandra
Message 1 of 16 in “Support triangular workflows”
  1. 0/4 Support triangular workflowsRamkumar Ramachandra, Mar 18, 2013
  2. 1/4 remote.c: simply a bit of code using git_config_string()Ramkumar Ramachandra, Mar 18, 2013
  3. Eric SunshineMar 18, 2013
  4. 2/4 remote.c: introduce a way to have different remotes for fetch/ pushRamkumar Ramachandra, Mar 18, 2013
  5. Jeff KingMar 18, 2013
  6. Ramkumar RamachandraMar 18, 2013
  7. Jeff KingMar 18, 2013
  8. Eric SunshineMar 18, 2013
  9. 3/4 remote.c: introduce remote.pushdefaultRamkumar Ramachandra, Mar 18, 2013
  10. Eric SunshineMar 18, 2013
  11. 4/4 remote.c: introduce branch.<name>.pushremoteRamkumar Ramachandra, Mar 18, 2013
  12. Eric SunshineMar 18, 2013
  13. Jeff KingMar 18, 2013
  14. Ramkumar RamachandraMar 18, 2013
  15. Jeff KingMar 18, 2013
  16. Marc BranchaudMar 18, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.