Re: [RFC/PATCH 3/3] push: add separate 'downstream' branch

From: Junio C Hamano <gitster@pobox.com>
Date: May 16, 2013, 15:24 UTC
Message-ID: <7va9nv7xss.fsf@alter.siamese.dyndns.org>
In-Reply-To: <7vip2j8ozu.fsf@alter.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:

Show 20 quoted lines

> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
>> It doesn't make sense to push to the upstream branch, so create new
>> configurations for the notion of 'downstream' branch, which is basically
>> the branch to push to by default.
>
> It doesn't?  That depends.
>
> To people coming from (and people who are still using) central
> shared repository workflow, pushing to anywhere other than the
> upstream makes no sense.
>
> If qualified with something like "When using a triangular workflow
> to pull from one place and push to another place" in front, I can
> see why having a separate upstream and downstream makes sense, and...
>
>> The upstream branch is remote+merge, the downstream branch is
>> pushremote+push.
>
> ... this is a perfect explanation of what a downsream is.

After thinking about it, I do not think downstream is a good word to describe where you push to at all.

I'll have more on this topic but the above is the short of it for now.