Definition of “downstream” and “upstream”

by

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.

More Related Contents:

  1. How to perform better document version control on Excel files and SQL schema files
  2. How do I rename a local Git branch?
  3. How can I reset or revert a file to a specific revision?
  4. How to change the author and committer name and e-mail of multiple commits in Git?
  5. Git workflow and rebase vs merge questions
  6. Is there a way to get the git root directory in one command?
  7. Insert a commit before the root commit in Git?
  8. How can I get a list of Git branches, ordered by most recent commit?
  9. How do I find the next commit in Git? (child/children of ref)
  10. How do you make Git ignore files without using .gitignore?
  11. Are Git’s pack files deltas rather than snapshots?
  12. View a file in a different Git branch without changing branches
  13. What is the Git equivalent for revision number?
  14. Moving from CVS to Git: $Id$ equivalent?
  15. Should composer.lock be committed to version control?
  16. Git keyword substitution like those in Subversion?
  17. Git push: “fatal ‘origin’ does not appear to be a git repository – fatal Could not read from remote repository.”
  18. Git rebase – commit select in fork-point mode
  19. How can I push a local Git branch to a remote with a different name easily?
  20. Git On Custom SSH Port
  21. Should I add the Visual Studio 2015 .vs folder to source control?
  22. Git: How to squash all commits on branch
  23. Git: How to rebase to a specific commit?
  24. git reset asks ‘more?’
  25. How does git track source code moved between files?
  26. Push and pull my conda environment using git
  27. Git Interactive Merge?
  28. Git merge squash repeatedly
  29. How to derive application build version string with Git’s `describe` command?
  30. Commit a file to a Different Branch Without Checkout

Leave a Comment