Google Git
Sign in
gerrit/git-repo/412367bfafd9de014cfeb37475e0f97b1f6a2509
commit
412367bfafd9de014cfeb37475e0f97b1f6a2509
[log] [tgz]
author
Peter Kjellerstedt <pkj@axis.com>
Sat Nov 08 00:06:16 2025 +0100
committer
LUCI <gerrit-scoped@luci-project-accounts.iam.gserviceaccount.com>
Wed Nov 26 02:07:35 2025 -0800
tree
100e674dea649546145dbb81532a8f432cc09f52
parent
47c24b5c4092ce397c94c05d8686c8bcac64fbb2 [diff]
project: Use dicts to keep track of copyfiles and linkfiles

This avoids copying/linking the same file/link multiple times if a
copyfile/linkfile element with the same values has been specifed
multiple times. This can happen when including a common manifest that
uses an extend-project element that has a copyfile/linkfile element.

This uses dicts rather than sets to store the copyfiles and linkfiles to
make sure the order they are specified in the manifest is maintained.
For Python 3.7+, maintaining the order that keys are added to dicts is
guaranteed, and for Python 3.6 it happened to be true.

The _CopyFile class and the _LinkFile class are changed to inherit from
NamedTuple to be able to store them in dicts.

Change-Id: I9f5a80298b875251a81c5fe7d353e262d104fae4
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/525322
Reviewed-by: Mike Frysinger <vapier@google.com>
Reviewed-by: Gavin Mak <gavinmak@google.com>
Tested-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Commit-Queue: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
4 files changed
tree: 100e674dea649546145dbb81532a8f432cc09f52
  1. .github/
  2. docs/
  3. hooks/
  4. man/
  5. release/
  6. subcmds/
  7. tests/
  8. .flake8
  9. .gitattributes
  10. .gitignore
  11. .gitreview
  12. .isort.cfg
  13. .mailmap
  14. .project
  15. .pydevproject
  16. color.py
  17. command.py
  18. completion.bash
  19. constraints.txt
  20. CONTRIBUTING.md
  21. editor.py
  22. error.py
  23. event_log.py
  24. fetch.py
  25. git_command.py
  26. git_config.py
  27. git_refs.py
  28. git_ssh
  29. git_superproject.py
  30. git_trace2_event_log.py
  31. git_trace2_event_log_base.py
  32. hooks.py
  33. LICENSE
  34. main.py
  35. MANIFEST.in
  36. manifest_xml.py
  37. pager.py
  38. platform_utils.py
  39. platform_utils_win32.py
  40. progress.py
  41. project.py
  42. pyproject.toml
  43. README.md
  44. repo
  45. repo_logging.py
  46. repo_trace.py
  47. requirements.json
  48. run_tests
  49. run_tests.vpython3
  50. run_tests.vpython3.8
  51. setup.py
  52. ssh.py
  53. tox.ini
  54. 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