From: scs@eskimo.com (Steve Summit)
To: git@vger.kernel.org
Cc: scs@eskimo.com
Subject: suggestion for git glossary: upstream, downstream
Date: Tue, 29 Dec 2020 08:15:56 -0500 [thread overview]
Message-ID: <2020Dec29.0815.scs.0001@quinine2.home> (raw)
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.)
next reply other threads:[~2020-12-29 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 13:15 Steve Summit [this message]
2021-01-04 23:57 ` suggestion for git glossary: upstream, downstream Junio C Hamano
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=2020Dec29.0815.scs.0001@quinine2.home \
--to=scs@eskimo.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).