Gavin Mak
bb9b4c2b60
GitRefs._LoadAll spawns `git for-each-ref` to load HEAD and refs/*, and Project._InitAnyMRef leaves warm snapshots stale after direct UpdateRef writes. On virtualized checkouts with thousands of repositories, these spawns add avoidable process overhead. Read HEAD, packed-refs, and loose refs directly in GitRefs when the repository uses a plain files ref backend, recording (mode, mtime, size, inode) stat tuples during the single directory pass and rechecking packed-refs afterward to guard against concurrent pack-refs updates. The tuples leave out ctime, which backup agents and file system crawlers move without changing a ref. Fall back to `git for-each-ref` when GIT_DIR, GIT_COMMON_DIR, reftable, commondir, custom refStorage config, symlinks, or lockfiles are present. Also add GitRefs.TryResolveRef for single-ref lookups without scanning all of refs/, GitRefs.Invalidate, and GitRefs.UpdateRef to keep cached snapshots warm after _InitAnyMRef writes a direct ref. Bug: 543101585 Change-Id: I804ac45712208e9f9e6437012661bc1de58b9825 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/655963 Tested-by: Gavin Mak <gavinmak@google.com> Reviewed-by: Brian Gan <brgan@google.com> Commit-Queue: Gavin Mak <gavinmak@google.com>
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.
- Homepage: https://gerrit.googlesource.com/git-repo/
- Mailing list: repo-discuss on Google Groups
- Bug reports: https://issues.gerritcodereview.com/issues?q=is:open%20componentid:1370071
- Source: https://gerrit.googlesource.com/git-repo/
- Overview: https://source.android.com/source/developing.html
- Docs: https://source.android.com/source/using-repo.html
- repo Manifest Format
- repo Hooks
- Contributing
- Running Repo in Microsoft Windows
- GitHub mirror: https://github.com/GerritCodeReview/git-repo
- Postsubmit tests: https://github.com/GerritCodeReview/git-repo/actions
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
Shell Completion
Repo includes completion scripts for Bash and Zsh.
Bash
To enable completion in Bash, source completion.bash in your ~/.bashrc:
source /path/to/git-repo/completion.bash
Zsh
To enable completion in Zsh, you can either:
-
Copy or symlink
completion.zshto a file named_repoin a directory in your$fpath:mkdir -p ~/.zsh/completion # You can copy the file: cp /path/to/git-repo/completion.zsh ~/.zsh/completion/_repo # Or symlink it: ln -s /path/to/git-repo/completion.zsh ~/.zsh/completion/_repoThen add that directory to your
fpathin~/.zshrcbeforecompinit:fpath=(~/.zsh/completion $fpath) autoload -Uz compinit compinit -
Or source the file directly and call
compdefin your~/.zshrc:source /path/to/git-repo/completion.zsh compdef _repo repo