Google Git
Sign in
gerrit / git-repo / e0b16a22a01c54a00a9e4a0c53dddfce3b0d59d6
commite0b16a22a01c54a00a9e4a0c53dddfce3b0d59d6[log] [tgz]
authorXin Li <delphij@google.com>Sun Sep 26 23:20:32 2021 -0700
committerXin Li <delphij@google.com>Mon Sep 27 06:36:05 2021 +0000
tree7759c55cdbe045de3974be17bc3a5557d42619db
parentd669d2dee5bd7986593d5df1dd8a736778501bbf [diff]
superproject: support a new revision attribute.

Tested:
$ ./run_tests

Verified that a manifest that specified superproject revision would use
the specified revision, and superproject will use the default revision.

Note that this is a slight behavior change from earlier repo versions,
which would always use the branch name of the manifest itself. However,
the new behavior would be more consisitent with regular "project"
element and would allow superproject be used even if it is not enabled
for the particular manifest branch, so we have decided to make the
change as it would provide more flexibility and better matches what
other elements would do.

Bug: [google internal] b/187868160
Change-Id: I35255ee347aff6e65179f7879d52931f168b477e
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/317643
Tested-by: Xin Li <delphij@google.com>
Reviewed-by: Raman Tenneti <rtenneti@google.com>
Reviewed-by: Mike Frysinger <vapier@google.com>
5 files changed
tree: 7759c55cdbe045de3974be17bc3a5557d42619db
  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