projects / thirdparty / git.git / blame
| Commit | Line | Data |
|---|---|---|
| 215a7ad1 JH |
1 | git-revert(1) |
| 2 | ============= | |
| 7fc9d69f JH |
3 | |
| 4 | NAME | |
| 5 | ---- | |
| 215a7ad1 | 6 | git-revert - Revert an existing commit. |
| 7fc9d69f JH |
7 | |
| 8 | SYNOPSIS | |
| 9 | -------- | |
| 215a7ad1 | 10 | 'git-revert' [-n] <commit> |
| 7fc9d69f JH |
11 | |
| 12 | DESCRIPTION | |
| 13 | ----------- | |
| 52a22d1e LAS |
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). | |
| 7fc9d69f JH |
17 | |
| 18 | OPTIONS | |
| 19 | ------- | |
| 52a22d1e LAS |
20 | <commit>:: |
| 21 | Commit to revert. | |
| 7fc9d69f | 22 | |
| de2b82c6 JH |
23 | -n:: |
| 24 | Usually the command automatically creates a commit with | |
| 25 | a commit log message stating which commit was reverted. | |
| 26 | This flag applies the change necessary to revert the | |
| 27 | named commit to your working tree, but does not make the | |
| 28 | commit. In addition, when this option is used, your | |
| 29 | working tree does not have to match the HEAD commit. | |
| 30 | The revert is done against the beginning state of your | |
| 31 | working tree. | |
| df8baa42 JF |
32 | + |
| 33 | This is useful when reverting more than one commits' | |
| 34 | effect to your working tree in a row. | |
| de2b82c6 JH |
35 | |
| 36 | ||
| 7fc9d69f JH |
37 | Author |
| 38 | ------ | |
| 39 | Written by Junio C Hamano <junkio@cox.net> | |
| 40 | ||
| 41 | Documentation | |
| 42 | -------------- | |
| 43 | Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>. | |
| 44 | ||
| 45 | GIT | |
| 46 | --- | |
| a7154e91 | 47 | Part of the gitlink:git[7] suite |
| 7fc9d69f | 48 |