To make edits to changes 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 change ID inside the brackets:
# Replacing 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 change numbers in the brackets to add a new patch set.
# To create a new change record, leave the brackets empty.
After the upload is complete the changes 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 outstanding changes between commit and working tree using git diff.
download
re
po download <TARGET> <CHANGE>
Downloads the specified change from the review system and makes it available in your project's local working directory.
For example, to download change 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 mirroring lag between when a change 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 following 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 tracking 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 binding pipes to the command's stdin, stdout, and sterr streams, and piping all output into a continuous stream that is displayed in a single 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, starting from the revision specified in the manifest.
The <BRANCH_NAME> argument should provide a short description of the change you are trying to make to the projects.If you don't know, consider using 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 working directory.
status
re
po status [<PROJECT_LIST>]
Compares the working tree to the staging 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 staging area differs from the last committed state.
letter meaning description
- no change 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 changed in index
C copied not in HEAD, copied from another in index
T mode changed same content in HEAD and index, mode changed
U unmerged conflict between HEAD and index; resolution required
In the second column, a lowercase letter indicates how the working directory differs from the index.
letter meaning 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:
扫一扫
5004
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
