Sorry for the large distribution. All contributors should rename their repos if they use "upstream", see https://github.com/D-Programming-Language/tools/pull/98#issuecomment-31289358.

It's my bad - apologies. Let's get this sorted quickly once and for all.


Andrei
_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals

Exactly what remote setup are you recommending?


On Sat, Dec 28, 2013 at 2:42 PM, Andrei Alexandrescu <andrei@erdani.com>wrote:

> Sorry for the large distribution. All contributors should rename their repos if they use "upstream", see https://github.com/D- Programming-Language/tools/pull/98#issuecomment-31289358.
>
> It's my bad - apologies. Let's get this sorted quickly once and for all.
>
>
> Andrei
> _______________________________________________
> phobos mailing list
> phobos@puremagic.com
> http://lists.puremagic.com/mailman/listinfo/phobos
>

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


Andrei

On 12/27/13 7:50 PM, Daniel Murphy wrote:
> Exactly what remote setup are you recommending?
>
>
> On Sat, Dec 28, 2013 at 2:42 PM, Andrei Alexandrescu <andrei@erdani.com
> <mailto:andrei@erdani.com>> wrote:
>
>     Sorry for the large distribution. All contributors should rename
>     their repos if they use "upstream", see
>     https://github.com/D-__Programming-Language/tools/__pull/98#issuecomment-31289358
>     <https://github.com/D-Programming-Language/tools/pull/98#issuecomment-31289358>.
>
>     It's my bad - apologies. Let's get this sorted quickly once and for all.
>
>
>     Andrei
>     _________________________________________________
>     phobos mailing list
>     phobos@puremagic.com <mailto:phobos@puremagic.com>
>     http://lists.puremagic.com/__mailman/listinfo/phobos
>     <http://lists.puremagic.com/mailman/listinfo/phobos>
>
>
>
>
> _______________________________________________
> dmd-internals mailing list
> dmd-internals@puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-internals
>
_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals

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@github.com:quickfur/tools.git (fetch)
origin	git@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?


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

I'm not sure what this has to do with this particular pull request, though.


T


-- 
Skill without imagination is craftsmanship and gives us many useful objects such as wickerwork picnic baskets.  Imagination without skill gives us modern art. -- Tom Stoppard
_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals

On Sat, Dec 28, 2013 at 5:17 PM, H. S. Teoh <hsteoh@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@github.com:quickfur/tools.git (fetch)
> origin  git@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.

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@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@github.com:quickfur/tools.git (fetch)
> > origin  git@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@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@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals

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@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@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@github.com:quickfur/tools.git (fetch)
> > > origin  git@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@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@puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-internals
>

Daniel Murphy, el 28 de December a las 23:27 me escribiste:
> The pull is now done with the full repo url, completely bypassing any stored remotes.

Perfect, thanks!


-- 
Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
3 people die every year, testing if a 9 volts battery works on their
tongue
_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals

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@llucax.com.ar
> <mailto:luca@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@quickfur.ath.cx <mailto:hsteoh@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@github.com:quickfur/tools.git (fetch)
>      > > origin  git@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@puremagic.com <mailto:dmd-internals@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@puremagic.com <mailto:dmd-internals@puremagic.com>
>     http://lists.puremagic.com/mailman/listinfo/dmd-internals
>
>
>
>
> _______________________________________________
> dmd-internals mailing list
> dmd-internals@puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-internals
>
_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals