“下游”的定义和“上游” [英] Definition of "downstream" and "upstream"

问题描述

我已经开始玩Git，并且遇到了上游和下游的条款。我以前见过这些，但从未完全理解它们。这些术语在SCM和源代码的背景下意味着什么？

解决方案

在源代码控制方面， strong> downstream ，当您从存储库复制（克隆，签出等）时。信息流向您的下游。

当您进行更改时，您通常希望将它们发回上游，以便它们进入该存储库以便每个从同一个来源获取的所有人都可以进行所有相同的更改。这主要是每个人如何协调工作的社会问题，而不是源控制的技术要求。您希望将您的更改纳入主项目中，以避免跟踪不同的开发线。

有时您会阅读关于包装或发布经理（人员，不是工具）谈论提交对上游的更改。这通常意味着他们必须调整原始来源，以便为他们的系统创建一个包。他们不希望继续进行这些更改，所以如果他们将这些更改上游发送给原始来源，他们不应该在下一个版本中处理同一问题。

I've started playing with Git and have come across the terms "upstream" and "downstream". I've seen these before but never understand them fully. What do these terms mean in the context of SCMs and source code?

解决方案

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.

这篇关于“下游”的定义和“上游”的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！