Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- 2.0.1 → 2.3.1 no changes
- 2.0.0 05/28/14
- 220.127.116.11 → 1.9.5 no changes
- 18.104.22.168 01/13/14
- 22.214.171.124 → 126.96.36.199 no changes
- 1.8.5 11/27/13
- 188.8.131.52 → 184.108.40.206 no changes
- 1.8.3 05/24/13
- 220.127.116.11 → 18.104.22.168 no changes
- 22.214.171.124 05/25/12
- 126.96.36.199 → 188.8.131.52 no changes
- 1.7.8 12/02/11
- 184.108.40.206 → 220.127.116.11 no changes
- 1.7.7 09/30/11
- 18.104.22.168 → 22.214.171.124 no changes
- 126.96.36.199 09/12/11
- 188.8.131.52 no changes
- 184.108.40.206 08/24/11
git-revert(1) Manual Page
git-revert - Revert some existing commits
git revert [--edit | --no-edit] [-n] [-m parent-number] [-s] <commit>...
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). If you want to throw away all uncommitted changes in your working directory, you should see git-reset(1), particularly the --hard option. If you want to extract specific files as they were in another commit, you should see git-checkout(1), specifically the git checkout <commit> -- <filename> syntax. Take care with these alternatives as both will discard uncommitted changes in your working directory.
Commits to revert. For a more complete list of ways to spell commit names, see gitrevisions(1). Sets of commits can also be given but no traversal is done by default, see git-rev-list(1) and its --no-walk option.
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 for more details.
With this option, git revert will not start the commit message editor.
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.
Add Signed-off-by line at the end of the commit message.
- git revert HEAD~3
Revert 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.
Written by Junio C Hamano <email@example.com>
Documentation by Junio C Hamano and the git-list <firstname.lastname@example.org>.
Part of the git(1) suite