Gavin Mak
af53524261
Phased sync orders each fetch batch slowest-first using `.repo_fetchtimes.json`, whereas interleaved sync dispatched each hierarchical level in path order, letting slow projects near the end of a level start late and extend the tail of the sync. Combining fetch and checkout times into `.repo_fetchtimes.json` would mix units with phased mode and older repo versions, and cause `-n` or `-l` runs to either skew full-sync estimates or sort by the wrong phase. Keep fetch and checkout estimates separate instead: - Parameterize `_SyncTimes` by filename and track fetch durations in `.repo_fetchtimes.json` and checkout durations in `.repo_checkouttimes.json`, recording a phase only when it succeeds. - Sort each interleaved level slowest-first by the phases active in `opt` (fetch when not `-l`, checkout when not `-n` and the project has a worktree). - Sort each `_SafeCheckoutOrder` level in phased `_Checkout` by `_checkout_times` and save in `finally` so phased and interleaved runs maintain and use the same per-phase estimates. Bug: 543101585 Change-Id: Ie8b15a95ab2d8019b058d5f839a93501d0d85979 Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/657085 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