@@ -3,20 +3,22 @@ git-revert(1)
3
3
4
4
NAME
5
5
----
6
- git-revert - Revert an existing commit
6
+ git-revert - Revert some existing commits
7
7
8
8
SYNOPSIS
9
9
--------
10
- 'git revert' [--edit | --no-edit] [-n] [-m parent-number] [-s] <commit>
10
+ 'git revert' [--edit | --no-edit] [-n] [-m parent-number] [-s] <commit>...
11
11
12
12
DESCRIPTION
13
13
-----------
14
- Given one existing commit, revert the change the patch introduces, and record a
15
- new commit that records it. This requires your working tree to be clean (no
16
- modifications from the HEAD commit).
17
14
18
- Note: 'git revert' is used to record a new commit to reverse the
19
- effect of an earlier commit (often a faulty one). If you want to
15
+ Given one or more existing commits, revert the changes that the
16
+ related patches introduce, and record some new commits that record
17
+ them. This requires your working tree to be clean (no modifications
18
+ from the HEAD commit).
19
+
20
+ Note: 'git revert' is used to record some new commits to reverse the
21
+ effect of some earlier commits (often only a faulty one). If you want to
20
22
throw away all uncommitted changes in your working directory, you
21
23
should see linkgit:git-reset[1], particularly the '--hard' option. If
22
24
you want to extract specific files as they were in another commit, you
@@ -26,10 +28,13 @@ both will discard uncommitted changes in your working directory.
26
28
27
29
OPTIONS
28
30
-------
29
- <commit>::
30
- Commit to revert.
31
+ <commit>... ::
32
+ Commits to revert.
31
33
For a more complete list of ways to spell commit names, see
32
34
"SPECIFYING REVISIONS" section in linkgit:git-rev-parse[1].
35
+ Sets of commits can also be given but no traversal is done by
36
+ default, see linkgit:git-rev-list[1] and its '--no-walk'
37
+ option.
33
38
34
39
-e::
35
40
--edit::
@@ -59,11 +64,11 @@ more details.
59
64
60
65
-n::
61
66
--no-commit::
62
- Usually the command automatically creates a commit with
63
- a commit log message stating which commit was
64
- reverted. This flag applies the change necessary
65
- to revert the named commit to your working tree
66
- and the index, but does not make the commit . In addition,
67
+ Usually the command automatically creates some commits with
68
+ commit log messages stating which commits were
69
+ reverted. This flag applies the changes necessary
70
+ to revert the named commits to your working tree
71
+ and the index, but does not make the commits . In addition,
67
72
when this option is used, your index does not have to match
68
73
the HEAD commit. The revert is done against the
69
74
beginning state of your index.
@@ -75,6 +80,20 @@ effect to your index in a row.
75
80
--signoff::
76
81
Add Signed-off-by line at the end of the commit message.
77
82
83
+ EXAMPLES
84
+ --------
85
+ git revert HEAD~3::
86
+
87
+ Revert the changes specified by the fourth last commit in HEAD
88
+ and create a new commit with the reverted changes.
89
+
90
+ git revert -n master\~5..master~2::
91
+
92
+ Revert the changes done by commits from the fifth last commit
93
+ in master (included) to the third last commit in master
94
+ (included), but do not create any commit with the reverted
95
+ changes. The revert only modifies the working tree and the
96
+ index.
78
97
79
98
Author
80
99
------
@@ -84,6 +103,10 @@ Documentation
84
103
--------------
85
104
Documentation by Junio C Hamano and the git-list <
[email protected] >.
86
105
106
+ SEE ALSO
107
+ --------
108
+ linkgit:git-cherry-pick[1]
109
+
87
110
GIT
88
111
---
89
112
Part of the linkgit:git[1] suite
0 commit comments