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

问题描述

我开始使用 Git 并遇到过上游"和下游"这两个术语.我以前见过这些，但从未完全理解它们.这些术语在 SCM(软件配置管理工具)和源代码的上下文中是什么意思?

I've started playing with Git and have come across the terms "upstream" and "downstream". 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?

推荐答案

就源代码控制而言，当您从存储库复制(克隆、签出等)时，您处于下游.信息流向下游"给你.

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屋！