[dmd-internals] [phobos] Please rename your remote github repos

[Andrei Alexandrescu]

Yah, so... sorry for the distraction.

Andrei

On 12/28/13 4:27 AM, Daniel Murphy wrote:
> The pull is now done with the full repo url, completely bypassing any
> stored remotes.
>
>
> On Sat, Dec 28, 2013 at 11:20 PM, Leandro Lucarella <luca at llucax.com.ar
> <mailto:luca at llucax.com.ar>> wrote:
>
>     So, what's the status of this. If anything fails because the user name
>     a remote whatever they want, then something is broken. You shouldn't
>     force users to name their remotes in any way!
>
>
>     Daniel Murphy, el 28 de December a las 18:21 me escribiste:
>      > On Sat, Dec 28, 2013 at 5:17 PM, H. S. Teoh
>     <hsteoh at quickfur.ath.cx <mailto:hsteoh at quickfur.ath.cx>> wrote:
>      >
>      > > On Fri, Dec 27, 2013 at 07:55:34PM -0800, Andrei Alexandrescu
>     wrote:
>      > > > We've been using the remote name "upstream" instead of the
>     default
>      > > > "origin", and that's quickly becoming lava (some people first
>     clone
>      > > > our repos and then try to use update.sh etc leading to
>     confusion).
>      > > >
>      > > > So we should just use "upstream" for the mothership and call it a
>      > > > day. Each of us has their own fork for which I don't know of a
>      > > > standardized name (I call mine "myfork").
>      > > [...]
>      > >
>      > > I'm confused. I've had the tools repo forked and checked out, and I
>      > > haven't had a problem:
>      > >
>      > > $ git remote -v
>      > > origin  git at github.com:quickfur/tools.git (fetch)
>      > > origin  git at github.com:quickfur/tools.git (push)
>      > > upstream https://github.com/D-Programming-Language/tools.git(fetch)
>      > > upstream https://github.com/D-Programming-Language/tools.git (push)
>      > > $
>      > >
>      > > So what exactly am I supposed to rename here?
>      > >
>      > >
>      > This is all correct, you should rename nothing, unless you want to.
>      >
>      >
>      > >
>      > > At least as far as github conventions go (I can't speak for git
>     users in
>      > > general), your fork is usually tied to 'origin', and 'upstream'
>     refers
>      > > to the where it forked from. Usually, you'd pull from
>     'upstream' (the
>      > > 'official' repo, to get the latest updates), and push to
>     'origin' (your
>      > > fork, e.g., when making pull requests, or just syncing your
>     fork to the
>      > > latest official repo).
>      > >
>      > >
>      > Exactly.
>
>      > _______________________________________________
>      > dmd-internals mailing list
>      > dmd-internals at puremagic.com <mailto:dmd-internals at puremagic.com>
>      > http://lists.puremagic.com/mailman/listinfo/dmd-internals
>
>
>     --
>     Leandro Lucarella (AKA luca) http://llucax.com.ar/
>     ----------------------------------------------------------------------
>     GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
>     ----------------------------------------------------------------------
>     I'll take a quiet life,
>     a handshake of carbon monoxide,
>     with no alarms and no surprises,
>     no alarms and no surprises.
>     _______________________________________________
>     dmd-internals mailing list
>     dmd-internals at puremagic.com <mailto:dmd-internals at puremagic.com>
>     http://lists.puremagic.com/mailman/listinfo/dmd-internals
>
>
>
>
> _______________________________________________
> dmd-internals mailing list
> dmd-internals at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-internals
>