table of contents
other versions
- wheezy 1:1.7.10.4-1+wheezy3
- wheezy-backports 1:1.9.1-1~bpo70+2
- jessie 1:2.1.4-2.1+deb8u2
- jessie-backports 1:2.11.0-3~bpo8+1
- testing 1:2.11.0-3
- unstable 1:2.11.0-4
- experimental 1:2.13.1+next.20170610-1
GIT-REVERT(1) | Git Manual | GIT-REVERT(1) |
NAME¶
git-revert - Revert some existing commitsSYNOPSIS¶
git revert [--edit | --no-edit] [-n] [-m parent-number] [-s] <commit>... git revert --continue git revert --quit git revert --abort
DESCRIPTION¶
Given one or more existing commits, revert the changes that the related patches introduce, and record some new commits that record them. This requires your working tree to be clean (no modifications from the HEAD commit).OPTIONS¶
<commit>...Commits to revert. For a more complete list of
ways to spell commit names, see gitrevisions(7). Sets of commits can
also be given but no traversal is done by default, see git-rev-list(1)
and its --no-walk option.
-e, --edit
With this option, git revert will let
you edit the commit message prior to committing the revert. This is the
default if you run the command from a terminal.
-m parent-number, --mainline parent-number
Usually you cannot revert a merge because you
do not know which side of the merge should be considered the mainline. This
option specifies the parent number (starting from 1) of the mainline and
allows revert to reverse the change relative to the specified parent.
Reverting a merge commit declares that you will never want the tree changes
brought in by the merge. As a result, later merges will only bring in tree
changes introduced by commits that are not ancestors of the previously
reverted merge. This may or may not be what you want.
See the revert-a-faulty-merge How-To[1] for more details.
--no-edit
With this option, git revert will not
start the commit message editor.
-n, --no-commit
Usually the command automatically creates some
commits with commit log messages stating which commits were reverted. This
flag applies the changes necessary to revert the named commits to your working
tree and the index, but does not make the commits. In addition, when this
option is used, your index does not have to match the HEAD commit. The revert
is done against the beginning state of your index.
This is useful when reverting more than one commits' effect to your index in a
row.
-s, --signoff
Add Signed-off-by line at the end of the
commit message.
--strategy=<strategy>
Use the given merge strategy. Should only be
used once. See the MERGE STRATEGIES section in git-merge(1) for
details.
-X<option>, --strategy-option=<option>
Pass the merge strategy-specific option
through to the merge strategy. See git-merge(1) for details.
SEQUENCER SUBCOMMANDS¶
--continueContinue the operation in progress using the
information in .git/sequencer. Can be used to continue after resolving
conflicts in a failed cherry-pick or revert.
--quit
Forget about the current operation in
progress. Can be used to clear the sequencer state after a failed cherry-pick
or revert.
--abort
Cancel the operation and return to the
pre-sequence state.
EXAMPLES¶
git revert HEAD~3Revert the changes specified by the fourth
last commit in HEAD and create a new commit with the reverted changes.
git revert -n master~5..master~2
Revert the changes done by commits from the
fifth last commit in master (included) to the third last commit in master
(included), but do not create any commit with the reverted changes. The revert
only modifies the working tree and the index.
SEE ALSO¶
git-cherry-pick(1)GIT¶
Part of the git(1) suiteNOTES¶
- 1.
- revert-a-faulty-merge How-To
03/19/2016 | Git 1.7.10.4 |