Re: [PATCH 0/4] Support triangular workflows

From: Jeff King <peff@peff.net>
Date: Mar 18, 2013, 14:25 UTC
Message-ID: <20130318142526.GA23075@sigill.intra.peff.net>
In-Reply-To: <1363612575-7340-1-git-send-email-artagnon@gmail.com>

On Mon, Mar 18, 2013 at 06:46:11PM +0530, Ramkumar Ramachandra wrote:

Show 8 quoted lines

> 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.

Yeah, I agree that it does not have much point, aside from people who have an unreasonable aversion to using the word "origin". There was a series posted last summer to add remote.default:

  http://article.gmane.org/gmane.comp.version-control.git/201065

It ended up stalled and never got merged. I think the main impetus was that "git clone -o foo" should leave "foo" in remote.default (of course, that still leaves unanswered why anyone would really want to use "-o foo" in the first place).

I think the symmetry makes some sense, but I also think it can come later if somebody wants it.

Show 5 quoted lines

>  Documentation/config.txt | 23 ++++++++++++++++---
>  builtin/push.c           |  2 +-
>  remote.c                 | 60 +++++++++++++++++++++++++++++++++++-------------
>  remote.h                 |  1 +
>  4 files changed, 66 insertions(+), 20 deletions(-)

No new tests?

-Peff