Linux "git-revert" Command Line Options and Examples
Revert some existing commits

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). Note: git revert is used to record some new commits to reverse the effect of some earlier commits (often only a faulty one).


Usage:

git revert [--[no-]edit] [-n] [-m parent-number] [-s] [-S[]] ...
    git revert --continue
    git revert --quit
    git revert --abort






Command Line Options:

-e
With this option, git revert will let you edit the commit message prior to committing the revert. This is the default if you runthe command from a terminal.
git-revert -e ...
-m
Usually you cannot revert a merge because you do not know which side of the merge should be considered the mainline. This optionspecifies the parent number (starting from 1) of the mainline and allows revert to reverse the change relative to the specifiedparent.Reverting a merge commit declares that you will never want the tree changes brought in by the merge. As a result, later mergeswill only bring in tree changes introduced by commits that are not ancestors of the previously reverted merge. This may or maynot be what you want.See the revert-a-faulty-merge How-To[1] for more details.
git-revert -m ...
--no-edit
With this option, git revert will not start the commit message editor.
git-revert --no-edit ...
-n
Usually the command automatically creates some commits with commit log messages stating which commits were reverted. This flagapplies the changes necessary to revert the named commits to your working tree and the index, but does not make the commits. Inaddition, when this option is used, your index does not have to match the HEAD commit. The revert is done against the beginningstate of your index.This is useful when reverting more than one commits' effect to your index in a row.
git-revert -n ...
-S[<keyid>]
GPG-sign commits. The keyid argument is optional and defaults to the committer identity; if specified, it must be stuck to theoption without a space.
git-revert -S[<keyid>] ...
-s
Add Signed-off-by line at the end of the commit message. See the signoff option in git-commit(1) for more information.
git-revert -s ...
--strategy
Use the given merge strategy. Should only be used once. See the MERGE STRATEGIES section in git-merge(1) for details.
git-revert --strategy ...
-X<option>
Pass the merge strategy-specific option through to the merge strategy. See git-merge(1) for details.SEQUENCER SUBCOMMANDS
git-revert -X<option> ...
--continue
Continue the operation in progress using the information in .git/sequencer. Can be used to continue after resolving conflicts ina failed cherry-pick or revert.
git-revert --continue ...
--quit
Forget about the current operation in progress. Can be used to clear the sequencer state after a failed cherry-pick or revert.
git-revert --quit ...
--abort
Cancel the operation and return to the pre-sequence state.EXAMPLESgit 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~2Revert 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.
git-revert --abort ...