Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- 2.0.1 → 2.1.0 no changes
- 2.0.0 05/28/14
- 188.8.131.52 → 1.9.4 no changes
- 184.108.40.206 01/13/14
- 220.127.116.11 → 18.104.22.168 no changes
- 1.8.5 11/27/13
- 22.214.171.124 → 126.96.36.199 no changes
- 1.8.3 05/24/13
- 188.8.131.52 → 184.108.40.206 no changes
- 220.127.116.11 05/25/12
- 18.104.22.168 → 22.214.171.124 no changes
- 1.7.8 12/02/11
- 126.96.36.199 → 188.8.131.52 no changes
- 1.7.7 09/30/11
- 184.108.40.206 → 220.127.116.11 no changes
- 18.104.22.168 09/12/11
- 22.214.171.124 no changes
- 126.96.36.199 08/24/11
- 188.8.131.52 → 1.7.6 no changes
- 1.7.5 04/24/11
git-revert(1) Manual Page
git-revert - Revert an existing commit
git revert [--edit | --no-edit] [-n] [-m parent-number] [-s] <commit>
Given one existing commit, revert the change the patch introduces, and record a new commit that records it. This requires your working tree to be clean (no modifications from the HEAD commit).
Note: git revert is used to record a new commit to reverse the effect of an earlier commit (often 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.
Commit to revert. For a more complete list of ways to spell commit names, see "SPECIFYING REVISIONS" section in git-rev-parse(1).
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 a commit with a commit log message stating which commit was reverted. This flag applies the change necessary to revert the named commit to your working tree and the index, but does not make the commit. 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.
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