Google Git
Sign in
gerrit / git-repo / b750b48f50eb4a11087ca6775161d5bf4d5c47d5
commitb750b48f50eb4a11087ca6775161d5bf4d5c47d5[log] [tgz]
authorLaMont Jones <lamontjones@google.com>Thu Aug 18 07:20:57 2022 -0400
committerLaMont Jones <lamontjones@google.com>Thu Oct 27 21:59:09 2022 +0000
treed3d3a7d6d021e1547d9f22875aea57a717540f92
parent6c8b894d8d06c8b1bf852b52676ee055a21718d6 [diff]
init: add --manifest-depth for shallow manifest clone

People rarely care about the history of the manifest repo.  Add a
parameter to specify depth for the manifest.

For now, make the default behavior the same as the current behavior.  At
a future date, the default will be changed to 1.  People who need the
full history should begin passing --manifest-depth=0 to preserve the
behavior when the default changes.

We can't reuse the existing --depth option because that applies to
all projects we clone, not just the manifest repo.

Bug: https://crbug.com/gerrit/16193, https://crbug.com/gerrit/16358
Change-Id: I9130fed3eaed656435c778a85cfe9d04e3a4a6a0
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/349814
Tested-by: LaMont Jones <lamontjones@google.com>
Reviewed-by: Xin Li <delphij@google.com>
5 files changed
tree: d3d3a7d6d021e1547d9f22875aea57a717540f92
  1. .github/
  2. docs/
  3. hooks/
  4. man/
  5. release/
  6. subcmds/
  7. tests/
  8. .flake8
  9. .gitattributes
  10. .gitignore
  11. .gitreview
  12. .mailmap
  13. .project
  14. .pydevproject
  15. color.py
  16. command.py
  17. completion.bash
  18. editor.py
  19. error.py
  20. event_log.py
  21. fetch.py
  22. git_command.py
  23. git_config.py
  24. git_refs.py
  25. git_ssh
  26. git_superproject.py
  27. git_trace2_event_log.py
  28. gitc_utils.py
  29. hooks.py
  30. LICENSE
  31. main.py
  32. MANIFEST.in
  33. manifest_xml.py
  34. pager.py
  35. platform_utils.py
  36. platform_utils_win32.py
  37. progress.py
  38. project.py
  39. README.md
  40. repo
  41. repo_trace.py
  42. requirements.json
  43. run_tests
  44. setup.py
  45. ssh.py
  46. SUBMITTING_PATCHES.md
  47. tox.ini
  48. 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