Google Git
Sign in
pigweed / third_party / gerrit / git-repo / refs/tags/v2.16.3
tag1dfa20972e7426f431b2d661c9378a51a3dba625
taggerXin Li <delphij@google.com>Thu Jul 22 20:04:33 2021 -0700
object8e983bbc0f5f48aa38d0e1c5a37766ce121d28eb 
repo v2.16.3
commit8e983bbc0f5f48aa38d0e1c5a37766ce121d28eb[log] [tgz]
authorXin Li <delphij@google.com>Tue Jul 20 20:15:30 2021 +0000
committerXin Li <delphij@google.com>Tue Jul 20 23:26:01 2021 +0000
tree36a0f156613796dc4a24ea84d0f31833f0368d62
parentc34b91c9d80d6d6510c500cb8a8a9ee448963f09 [diff]
Force a fetch when superproject has a newer SHA1 for remote branch.

For older git-repo versions, we might have only fetched the SHA1
revision that was provided by the project, but have remote branch left
intact as long as they exist. When the remote branch become stale,
some repo operations like rebase would fail, and repo sync would not
correct this situation.

Fix this by tightening the requirement to also require the superproject
provided SHA1 be an ancestor or equal to the tip-of-tree of the remote
branch.

Bug: [google internal] b/193798453
Change-Id: Ie34c5d860dabb1cbd9f822da929088ec69c79cf6
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/312642
Tested-by: Xin Li <delphij@google.com>
Reviewed-by: Raman Tenneti <rtenneti@google.com>
1 file changed
tree: 36a0f156613796dc4a24ea84d0f31833f0368d62
  1. .github/
  2. docs/
  3. hooks/
  4. man/
  5. release/
  6. subcmds/
  7. tests/
  8. .flake8
  9. .gitattributes
  10. .gitignore
  11. .mailmap
  12. .project
  13. .pydevproject
  14. color.py
  15. command.py
  16. completion.bash
  17. editor.py
  18. error.py
  19. event_log.py
  20. git_command.py
  21. git_config.py
  22. git_refs.py
  23. git_ssh
  24. git_superproject.py
  25. git_trace2_event_log.py
  26. gitc_utils.py
  27. hooks.py
  28. LICENSE
  29. main.py
  30. MANIFEST.in
  31. manifest_xml.py
  32. pager.py
  33. platform_utils.py
  34. platform_utils_win32.py
  35. progress.py
  36. project.py
  37. README.md
  38. repo
  39. repo_trace.py
  40. requirements.json
  41. run_tests
  42. setup.py
  43. ssh.py
  44. SUBMITTING_PATCHES.md
  45. tox.ini
  46. wrapper.py
README.md

repo

Repo is a tool built on top of Git. Repo helps manage many Git repositories, does the uploads to revision control systems, and automates parts of the development workflow. Repo is not meant to replace Git, only to make it easier to work with Git. The repo command is an executable Python script that you can put anywhere in your path.

Contact

Please use the repo-discuss mailing list or issue tracker for questions.

You can file a new bug report under the “repo” component.

Please do not e-mail individual developers for support. They do not have the bandwidth for it, and often times questions have already been asked on repo-discuss or bugs posted to the issue tracker. So please search those sites first.

Install

Many distros include repo, so you might be able to install from there.

# Debian/Ubuntu.
$ sudo apt-get install repo

# Gentoo.
$ sudo emerge dev-vcs/repo

You can install it manually as well as it's a single script.

$ mkdir -p ~/.bin
$ PATH="${HOME}/.bin:${PATH}"
$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/.bin/repo
$ chmod a+rx ~/.bin/repo