git - “下游”和“上游”的定义(Definition of “downstream” and “upstream”)

Question

I've started playing with Git and have come across the terms "upstream" and "downstream".

(我已经开始玩Git并遇到过“上游”和“下游”这两个词。)

I've seen these before but never understood them fully.

(我之前见过这些，但从未完全理解它们。)

What do these terms mean in the context of SCMs ( Software Configuration Management tools) and source code?

(这些术语在SCM（ 软件配置管理工具）和源代码的上下文中意味着什么？)

  ask by brendan translate from so

Answer 1

In terms of source control, you're " downstream " when you copy (clone, checkout, etc) from a repository.

(在源代码控制方面，当您从存储库复制（克隆，签出等）时，您处于“ 下游 ”。)

Information flowed "downstream" to you.

(信息流向“下游”给您。)

When you make changes, you usually want to send them back " upstream " so they make it into that repository so that everyone pulling from the same source is working with all the same changes.

(当您进行更改时，您通常希望将它们发送回“ 上游 ”，以便它们进入该存储库，以便从同一来源拉出的每个人都在处理所有相同的更改。)

This is mostly a social issue of how everyone can coordinate their work rather than a technical requirement of source control.

(这主要是每个人如何协调工作而不是源控制技术要求的社会问题。)

You want to get your changes into the main project so you're not tracking divergent lines of development.

(您希望将更改纳入主项目，这样您就无法跟踪不同的开发线。)

Sometimes you'll read about package or release managers (the people, not the tool) talking about submitting changes to "upstream".

(有时您会阅读有关提交“上游”更改的包或发布经理（人员，而不是工具）。)

That usually means they had to adjust the original sources so they could create a package for their system.

(这通常意味着他们必须调整原始来源，以便他们可以为他们的系统创建一个包。)

They don't want to keep making those changes, so if they send them "upstream" to the original source, they shouldn't have to deal with the same issue in the next release.

(他们不想继续进行这些更改，因此如果他们将它们“上游”发送到原始源，他们就不必在下一个版本中处理相同的问题。)