To make edits to cha
nges after they have been uploaded, you should use a tool like
git rebase -i or
git commit --amend to update your local commits. After your edits are complete:
Make sure the updated branch is the currently checked out branch.
For each commit in the series, enter the Gerrit cha
nge ID inside the brackets:
# Replaci
ng from branch foo
[ 3021 ] 35f2596c Refactor part of GetUploadableBranches to lookup one specific...
[ 2829 ] ec18b4ba Update proto client to sup
port patch set replacments
# Insert cha
nge numbers in the brackets to add a new patch set.
# To create a new cha
nge record, leave the brackets empty.
After the upload is complete the cha
nges will have an additional Patch Set.
If you only want to upload the currently checked out
Git branch, you can use the flag --current-branch (or --cbr for short).
diff
re
po diff [<PROJECT_LIST>]
Shows outstandi
ng cha
nges between commit and worki
ng tree usi
ng git diff.
download
re
po download <TARGET> <CHA
NGE>
Downloads the specified cha
nge from the review system and makes it available in your project's local worki
ng directory.
For example, to download cha
nge 23823 into your platform/build directory:
re
po download platform/build 23823
A re
po sync should effectively
remove any commits retrieved via re
po download. Or, you can check out the remote branch; e.g.,
git checkout m/master.
Note: There is a slight mirrori
ng lag between when a cha
nge is visible on the web in Gerrit and when re
po download will be able to find it for all users, because of replication delays to all servers worldwide.
forall
re
po forall [<PROJECT_LIST>] -c <COMMAND>
Executes the given shell command in each project. The followi
ng additional environment variables are made available by re
po forall:
RE
PO_PROJECT is set to the unique name of the project.
RE
PO_PATH is the path relative to the root of the client.
RE
PO_REMOTE is the name of the remote system from the manifest.
RE
PO_LREV is the name of the revision from the manifest, translated to a local tracki
ng branch. Used if you need to pass the manifest revision to a locally executed
git command.
RE
PO_RREV is the name of the revision from the manifest, exactly as written in the manifest.
Options:
-c: command and arguments to execute. The command is evaluated through /bin/sh and any arguments after it are passed through as shell
positional parameters.
-p: show project headers before output of the specified command. This is achieved by bindi
ng pipes to the command's stdin, stdout, and sterr streams, and pipi
ng all output into a continuous stream that is displayed in a si
ngle pager session.
-v: show messages the command writes to stderr.
prune
re
po prune [<PROJECT_LIST>]
Prunes (deletes) topics that are already merged.
start
re
po start <BRANCH_NAME> [<PROJECT_LIST>]
Begins a new branch for development, starti
ng from the revision specified in the manifest.
The <BRANCH_NAME> argument should provide a short description of the cha
nge you are tryi
ng to make to the projects.If you don't know, consider usi
ng the name default.
The <PROJECT_LIST> specifies which projects will participate in this topic branch.
Note: "." is a useful shorthand for the project in the current worki
ng directory.
status
re
po status [<PROJECT_LIST>]
Compares the worki
ng tree to the stagi
ng area (index) and the most recent commit on this branch (HEAD) in each project specified. Displays a summary line for each file where there is a difference between these three states.
To see the status for only the current branch, run re
po status. The status information will be listed by project. For each file in the project, a two-letter code is used:
In the first column, an uppercase letter indicates how the stagi
ng area differs from the last committed state.
letter meani
ng description
- no cha
nge same in HEAD and index
A added not in HEAD, in index
M modified in HEAD, modified in index
D deleted in HEAD, not in index
R renamed not in HEAD, path cha
nged in index
C copied not in HEAD, copied from another in index
T mode cha
nged same content in HEAD and index, mode cha
nged
U unmerged conflict between HEAD and index; resolution required
In the second column, a lowercase letter indicates how the worki
ng directory differs from the index.
letter meani
ng description
- new/unknown not in index, in work tree
m modified in index, in work tree, modified
d deleted in index, not in work tree
Was this page helpful? Let us know how we did:
6009
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
