From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH 3/3] push: add separate 'downstream' branch
Date: Thu, 16 May 2013 08:24:19 -0700 [thread overview]
Message-ID: <7va9nv7xss.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7vip2j8ozu.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Wed, 15 May 2013 22:36:53 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> 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.
next prev parent reply other threads:[~2013-05-16 15:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 3:43 [RFC/PATCH 0/3] New kind of upstream branch: downstream branch Felipe Contreras
2013-05-16 3:43 ` [RFC/PATCH 1/3] remote: don't override default if cur head remote is '.' Felipe Contreras
2013-05-16 3:43 ` [RFC/PATCH 2/3] pull: trivial cleanups Felipe Contreras
2013-05-16 8:29 ` Ramkumar Ramachandra
2013-05-16 8:56 ` Felipe Contreras
2013-05-16 9:34 ` Ramkumar Ramachandra
2013-05-16 9:36 ` Felipe Contreras
2013-05-16 9:54 ` Ramkumar Ramachandra
2013-05-16 10:15 ` Felipe Contreras
2013-05-16 10:18 ` Ramkumar Ramachandra
2013-05-16 10:24 ` Felipe Contreras
2013-05-16 11:54 ` Antoine Pelisse
2013-05-16 13:36 ` Felipe Contreras
2013-05-16 3:43 ` [RFC/PATCH 3/3] push: add separate 'downstream' branch Felipe Contreras
2013-05-16 5:36 ` Junio C Hamano
2013-05-16 6:00 ` Felipe Contreras
2013-05-16 6:14 ` Junio C Hamano
2013-05-16 15:24 ` Junio C Hamano [this message]
2013-05-16 8:21 ` Ramkumar Ramachandra
2013-05-16 9:05 ` Felipe Contreras
2013-05-16 9:20 ` Ramkumar Ramachandra
2013-05-16 9:33 ` Felipe Contreras
2013-05-16 10:06 ` Ramkumar Ramachandra
2013-05-16 10:22 ` Felipe Contreras
2013-05-16 11:31 ` Ramkumar Ramachandra
2013-05-16 13:32 ` Felipe Contreras
2013-05-16 13:52 ` Ramkumar Ramachandra
2013-05-16 14:53 ` Felipe Contreras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7va9nv7xss.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).