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

On Thu, May 16, 2013 at 12:36 AM, Junio C Hamano [off-list ref] wrote:

Felipe Contreras [off-list ref] writes:

quoted

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.

Semantics I guess; you can say they are pushing to the upstream, or
that they are pushing downstream, which happens to be the same as the
upstream.

My rationale was that at some point in the future we might want to
remove the code that pushes upstream, and only push downstream. And
either way configure downstream when creating new branches with
tracking. But I'm not sure that's a good idea.

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

quoted

The upstream branch is remote+merge, the downstream branch is
pushremote+push.

... this is a perfect explanation of what a downsream is.

Cool. I haven't decided how best to set the downstream yet, but for me
it's more important that 'git fetch' works sanely (patch #1), and I
don't like the proposed patch, but I can't think of anything better.

-- 
Felipe Contreras