From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git List <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>
Subject: [PATCH 0/4] Support triangular workflows
Date: Mon, 18 Mar 2013 18:46:11 +0530 [thread overview]
Message-ID: <1363612575-7340-1-git-send-email-artagnon@gmail.com> (raw)
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 reply other threads:[~2013-03-18 13:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 13:16 Ramkumar Ramachandra [this message]
2013-03-18 13:16 ` [PATCH 1/4] remote.c: simply a bit of code using git_config_string() Ramkumar Ramachandra
2013-03-18 22:14 ` Eric Sunshine
2013-03-18 13:16 ` [PATCH 2/4] remote.c: introduce a way to have different remotes for fetch/ push Ramkumar Ramachandra
2013-03-18 14:31 ` Jeff King
2013-03-18 14:56 ` Ramkumar Ramachandra
2013-03-18 14:58 ` Jeff King
2013-03-18 22:17 ` Eric Sunshine
2013-03-18 13:16 ` [PATCH 3/4] remote.c: introduce remote.pushdefault Ramkumar Ramachandra
2013-03-18 22:19 ` Eric Sunshine
2013-03-18 13:16 ` [PATCH 4/4] remote.c: introduce branch.<name>.pushremote Ramkumar Ramachandra
2013-03-18 22:23 ` Eric Sunshine
2013-03-18 14:25 ` [PATCH 0/4] Support triangular workflows Jeff King
2013-03-18 14:28 ` Ramkumar Ramachandra
2013-03-18 14:32 ` Jeff King
2013-03-18 15:55 ` Marc Branchaud
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1363612575-7340-1-git-send-email-artagnon@gmail.com \
--to=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).