Re: Relative submodule URLs

From: Robert Dailey <rcdailey.lists@gmail.com>
Date: Aug 19, 2014, 20:18 UTC
Message-ID: <CAHd499Ad3T1sHQWwE9NNySTbfaL_UvcdX4qrWkhH2PYhet=hMg@mail.gmail.com>
In-Reply-To: <xmqqoavguw26.fsf@gitster.dls.corp.google.com>

On Tue, Aug 19, 2014 at 2:19 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 11 quoted lines

>
> I do not know if that is how GitHub teaches people, but I would have
> to say that these are strange phrasing.  I suspect that part of
> their documentation was written long time ago, back when nobody on
> the GitHub side were involved in design (let alone implementation)
> of Git, and I would take it with a grain of salt.
>
> Having said that, here is a summary of the current support for
> referring to different repositories in Git:
>
> <snip>

Wow, that was a very good read. Thank you for that. I definitely have been using the wrong terms. upstream & origin are interchangeable, yet I was using them to represent two distinct repositories.

I think going forward my central repository will be named 'origin' and for the name of the second, nothing has really jumped out at me yet but it'll either be "fork" or "proxy"... "surrogate" would be nice too if it wasn't such a long word in comparison.

I'm sure you guys will find a name for it in good time. I wonder what Linus would suggest.