git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: scs@eskimo.com (Steve Summit)
Cc: git@vger.kernel.org
Subject: Re: suggestion for git glossary: upstream, downstream
Date: Mon, 04 Jan 2021 15:57:34 -0800	[thread overview]
Message-ID: <xmqqwnws1ci9.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: 2020Dec29.0815.scs.0001@quinine2.home

scs@eskimo.com (Steve Summit) writes:

> The terms "upstream" and "downstream" are heavily used in much
> writing about git, with obvious meanings and implications for
> those who use git regularly, but they're not defined at
> https://git-scm.com/docs/gitglossary .  Perhaps they should be?
> (Sorry, I'm not nearly experienced enough with git yet to write
> good definitions myself, though.)

Yup, 'upstream' has clear definition and we use the phrase a lot.
'downstream', not that much, primarily because your repository may
have its upstream (singular) but typically you may not even know the
set of people who consider your repository their upstream.

Having said that, there isn't much we can actually say about
'upstream' as a unversal truth, no?  I can readily think of this:

    Your upstream is the line(s) of history you base your
    development on.

but beyond that, there aren't much that is common across different
workflows how 'upstream' appears to you.  Sometimes you may ask your
changes to be pulled by it, sometimes you may directly push into it
while others like you who consider it their upstream do the same.

So...

      reply	other threads:[~2021-01-04 23:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29 13:15 suggestion for git glossary: upstream, downstream Steve Summit
2021-01-04 23:57 ` Junio C Hamano [this message]

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=xmqqwnws1ci9.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=scs@eskimo.com \
    /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).