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

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

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 28, 2013, 15:02 UTC
Message-ID
<7vppyjworw.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1364477202-5742-1-git-send-email-artagnon@gmail.com>
Ramkumar Ramachandra <artagnon@gmail.com> writes:
Show 14 quoted lines
> The changes in this round are:
>
> 1. Peff submitted a patch to squash into [3/6].  Since his patch
>    essentially reverts mine, I've blamed him for the change.
>
> 2. Peff suggested a code movement in [5/6] to make things flow more
>    naturally.
>
> 3. Jonathan suggested a better test description in [2/6].
>
> 4. Junio suggested a minor documentation update in [6/6].
>
> My build of git has had this feature for two weeks now (since the
> first iteration), and I'm very happy with it.
Will take a look; thanks for a reroll.

We may need a bit of adjustment to the longer term plan for the push.default topic, as I expect we will have this feature a lot sooner (e.g. perhaps in 1.8.4) than we will switch the push default to "simple". The description of simple and upstream still is written around the "you push to and pull from the same place", and may need to be updated to explain "what happens if you are employing a triangular workflow?" Or it could turn out that triangular people may be better served by a push.default different from simple or upstream.

Or it may turn out that we do not need any change to what is queued on the push-2.0-default-to-simple topic (I haven't thought things through).

It is not urgent, but please start thinking about how you can help, now you introduced the triangular stuff.

Thanks.
Show 16 quoted lines
> Jeff King (1):
>   t5516 (fetch-push): drop implicit arguments from helper functions
>
> Ramkumar Ramachandra (5):
>   remote.c: simplify a bit of code using git_config_string()
>   t5516 (fetch-push): update test description
>   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 |  24 +++-
>  builtin/push.c           |   2 +-
>  remote.c                 |  41 ++++--
>  remote.h                 |   1 +
>  t/t5516-fetch-push.sh    | 316 +++++++++++++++++++++++++++--------------------
>  5 files changed, 238 insertions(+), 146 deletions(-)
Previous: Ramkumar RamachandraNext: Jeff King
Message 8 of 18 in “Support triangular workflows”
  1. 0/6 Support triangular workflowsRamkumar Ramachandra, Mar 28, 2013
  2. 1/6 remote.c: simplify a bit of code using git_config_string()Ramkumar Ramachandra, Mar 28, 2013
  3. 2/6 t5516 (fetch-push): update test descriptionRamkumar Ramachandra, Mar 28, 2013
  4. 3/6 t5516 (fetch-push): drop implicit arguments from helper functionsRamkumar Ramachandra, Mar 28, 2013
  5. 4/6 remote.c: introduce a way to have different remotes for fetch/pushRamkumar Ramachandra, Mar 28, 2013
  6. 5/6 remote.c: introduce remote.pushdefaultRamkumar Ramachandra, Mar 28, 2013
  7. 6/6 remote.c: introduce branch.<name>.pushremoteRamkumar Ramachandra, Mar 28, 2013
  8. Junio C HamanoMar 28, 2013
  9. Jeff KingMar 28, 2013
  10. Junio C HamanoMar 28, 2013
  11. Ramkumar RamachandraMar 31, 2013
  12. Junio C HamanoApr 1, 2013
  13. Junio C HamanoApr 1, 2013
  14. Junio C HamanoApr 1, 2013
  15. Junio C HamanoApr 1, 2013
  16. Ramkumar RamachandraMar 31, 2013
  17. Jeff KingMar 31, 2013
  18. Junio C HamanoApr 1, 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.