しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 1 | git-stash(1) |
| 2 | ============ |
| 3 | |
| 4 | NAME |
| 5 | ---- |
| 6 | git-stash - Stash the changes in a dirty working directory away |
| 7 | |
| 8 | SYNOPSIS |
| 9 | -------- |
| 10 | [verse] |
Stephan Beyer | a5ab00c | 2008-08-16 05:27:31 +0200 | [diff] [blame] | 11 | 'git stash' list [<options>] |
Stephen Boyd | fcdd0e9 | 2009-06-17 18:07:37 -0700 | [diff] [blame] | 12 | 'git stash' show [<stash>] |
| 13 | 'git stash' drop [-q|--quiet] [<stash>] |
| 14 | 'git stash' ( pop | apply ) [--index] [-q|--quiet] [<stash>] |
Abhijit Menon-Sen | 656b503 | 2008-07-03 11:46:05 +0530 | [diff] [blame] | 15 | 'git stash' branch <branchname> [<stash>] |
Ramkumar Ramachandra | aa7e722 | 2013-06-15 18:43:23 +0530 | [diff] [blame] | 16 | 'git stash' [save [-p|--patch] [-k|--[no-]keep-index] [-q|--quiet] |
Junio C Hamano | c1ebd90 | 2013-08-14 09:53:43 -0700 | [diff] [blame] | 17 | [-u|--include-untracked] [-a|--all] [<message>]] |
Abhijit Menon-Sen | 656b503 | 2008-07-03 11:46:05 +0530 | [diff] [blame] | 18 | 'git stash' clear |
Ramkumar Ramachandra | 2be4351 | 2013-06-15 18:43:22 +0530 | [diff] [blame] | 19 | 'git stash' create [<message>] |
Ramkumar Ramachandra | bd514ca | 2013-06-15 18:43:25 +0530 | [diff] [blame] | 20 | 'git stash' store [-m|--message <message>] [-q|--quiet] <commit> |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 21 | |
| 22 | DESCRIPTION |
| 23 | ----------- |
| 24 | |
Thomas Rast | ca76828 | 2010-01-07 17:49:12 +0100 | [diff] [blame] | 25 | Use `git stash` when you want to record the current state of the |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 26 | working directory and the index, but want to go back to a clean |
| 27 | working directory. The command saves your local modifications away |
| 28 | and reverts the working directory to match the `HEAD` commit. |
| 29 | |
| 30 | The modifications stashed away by this command can be listed with |
Jonathan Nieder | 483bc4f | 2008-06-30 13:56:34 -0500 | [diff] [blame] | 31 | `git stash list`, inspected with `git stash show`, and restored |
| 32 | (potentially on top of a different commit) with `git stash apply`. |
| 33 | Calling `git stash` without any arguments is equivalent to `git stash save`. |
| 34 | A stash is by default listed as "WIP on 'branchname' ...", but |
しらいしななこ | ec96e0f | 2007-07-17 17:15:42 +0900 | [diff] [blame] | 35 | you can give a more descriptive message on the command line when |
| 36 | you create one. |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 37 | |
Jeff King | cc1b8d8 | 2010-02-17 20:16:20 -0500 | [diff] [blame] | 38 | The latest stash you created is stored in `refs/stash`; older |
Junio C Hamano | 9488e87 | 2007-07-01 15:29:01 -0700 | [diff] [blame] | 39 | stashes are found in the reflog of this reference and can be named using |
Jeff King | 6cf378f | 2012-04-26 04:51:57 -0400 | [diff] [blame] | 40 | the usual reflog syntax (e.g. `stash@{0}` is the most recently |
| 41 | created stash, `stash@{1}` is the one before it, `stash@{2.hours.ago}` |
Aaron M Watson | a56c8f5 | 2016-10-24 19:40:13 -0400 | [diff] [blame] | 42 | is also possible). Stashes may also be referenced by specifying just the |
| 43 | stash index (e.g. the integer `n` is equivalent to `stash@{n}`). |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 44 | |
| 45 | OPTIONS |
| 46 | ------- |
| 47 | |
John Marshall | c20aec0 | 2014-02-21 17:25:24 +0000 | [diff] [blame] | 48 | save [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q|--quiet] [<message>]:: |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 49 | |
Jonathan Nieder | b1889c3 | 2008-06-30 01:09:04 -0500 | [diff] [blame] | 50 | Save your local modifications to a new 'stash', and run `git reset |
Matthieu Moy | 3c2eb80 | 2009-08-18 23:38:40 +0200 | [diff] [blame] | 51 | --hard` to revert them. The <message> part is optional and gives |
| 52 | the description along with the stashed state. For quickly making |
| 53 | a snapshot, you can omit _both_ "save" and <message>, but giving |
| 54 | only <message> does not trigger this action to prevent a misspelled |
| 55 | subcommand from making an unwanted stash. |
SZEDER Gábor | 7bedebc | 2008-06-27 16:37:15 +0200 | [diff] [blame] | 56 | + |
| 57 | If the `--keep-index` option is used, all changes already added to the |
| 58 | index are left intact. |
Thomas Rast | dda1f2a | 2009-08-13 14:29:44 +0200 | [diff] [blame] | 59 | + |
David Caldwell | 7875130 | 2011-06-24 17:56:06 -0700 | [diff] [blame] | 60 | If the `--include-untracked` option is used, all untracked files are also |
| 61 | stashed and then cleaned up with `git clean`, leaving the working directory |
| 62 | in a very clean state. If the `--all` option is used instead then the |
| 63 | ignored files are stashed and cleaned in addition to the untracked files. |
| 64 | + |
Valentin Haenel | f2808a5 | 2011-05-05 20:48:47 +0200 | [diff] [blame] | 65 | With `--patch`, you can interactively select hunks from the diff |
Thomas Rast | dda1f2a | 2009-08-13 14:29:44 +0200 | [diff] [blame] | 66 | between HEAD and the working tree to be stashed. The stash entry is |
| 67 | constructed such that its index state is the same as the index state |
| 68 | of your repository, and its worktree contains only the changes you |
| 69 | selected interactively. The selected changes are then rolled back |
Valentin Haenel | f2808a5 | 2011-05-05 20:48:47 +0200 | [diff] [blame] | 70 | from your worktree. See the ``Interactive Mode'' section of |
Jeff King | 6cf378f | 2012-04-26 04:51:57 -0400 | [diff] [blame] | 71 | linkgit:git-add[1] to learn how to operate the `--patch` mode. |
Thomas Rast | dda1f2a | 2009-08-13 14:29:44 +0200 | [diff] [blame] | 72 | + |
| 73 | The `--patch` option implies `--keep-index`. You can use |
| 74 | `--no-keep-index` to override this. |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 75 | |
Miklos Vajna | fbd538c | 2008-02-20 12:31:35 +0100 | [diff] [blame] | 76 | list [<options>]:: |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 77 | |
| 78 | List the stashes that you currently have. Each 'stash' is listed |
Jeff King | 6cf378f | 2012-04-26 04:51:57 -0400 | [diff] [blame] | 79 | with its name (e.g. `stash@{0}` is the latest stash, `stash@{1}` is |
Junio C Hamano | 9488e87 | 2007-07-01 15:29:01 -0700 | [diff] [blame] | 80 | the one before, etc.), the name of the branch that was current when the |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 81 | stash was made, and a short description of the commit the stash was |
| 82 | based on. |
| 83 | + |
| 84 | ---------------------------------------------------------------- |
しらいしななこ | ec96e0f | 2007-07-17 17:15:42 +0900 | [diff] [blame] | 85 | stash@{0}: WIP on submit: 6ebd0e2... Update git-stash documentation |
| 86 | stash@{1}: On master: 9cc0589... Add git-stash |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 87 | ---------------------------------------------------------------- |
Miklos Vajna | fbd538c | 2008-02-20 12:31:35 +0100 | [diff] [blame] | 88 | + |
Thomas Rast | 0b444cd | 2010-01-10 00:33:00 +0100 | [diff] [blame] | 89 | The command takes options applicable to the 'git log' |
Thomas Rast | b7b1038 | 2009-10-19 17:48:12 +0200 | [diff] [blame] | 90 | command to control what is shown and how. See linkgit:git-log[1]. |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 91 | |
| 92 | show [<stash>]:: |
| 93 | |
Ralf Wildenhues | 06ada15 | 2007-10-09 23:00:03 +0200 | [diff] [blame] | 94 | Show the changes recorded in the stash as a diff between the |
Junio C Hamano | 9488e87 | 2007-07-01 15:29:01 -0700 | [diff] [blame] | 95 | stashed state and its original parent. When no `<stash>` is given, |
| 96 | shows the latest one. By default, the command shows the diffstat, but |
Thomas Rast | 0b444cd | 2010-01-10 00:33:00 +0100 | [diff] [blame] | 97 | it will accept any format known to 'git diff' (e.g., `git stash show |
Jeff King | 6cf378f | 2012-04-26 04:51:57 -0400 | [diff] [blame] | 98 | -p stash@{1}` to view the second most recent stash in patch form). |
Namhyung Kim | 3086c06 | 2015-08-30 00:25:57 +0900 | [diff] [blame] | 99 | You can use stash.showStat and/or stash.showPatch config variables |
| 100 | to change the default behavior. |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 101 | |
Stephen Boyd | fcdd0e9 | 2009-06-17 18:07:37 -0700 | [diff] [blame] | 102 | pop [--index] [-q|--quiet] [<stash>]:: |
Thomas Rast | d183663 | 2009-05-28 11:40:15 +0200 | [diff] [blame] | 103 | |
| 104 | Remove a single stashed state from the stash list and apply it |
| 105 | on top of the current working tree state, i.e., do the inverse |
| 106 | operation of `git stash save`. The working directory must |
| 107 | match the index. |
| 108 | + |
| 109 | Applying the state can fail with conflicts; in this case, it is not |
| 110 | removed from the stash list. You need to resolve the conflicts by hand |
| 111 | and call `git stash drop` manually afterwards. |
| 112 | + |
Miklos Vajna | 0bdcac5 | 2007-10-01 00:30:27 +0200 | [diff] [blame] | 113 | If the `--index` option is used, then tries to reinstate not only the working |
| 114 | tree's changes, but also the index's ones. However, this can fail, when you |
| 115 | have conflicts (which are stored in the index, where you therefore can no |
| 116 | longer apply the changes as they were originally). |
SZEDER Gábor | f39d6ee | 2009-06-09 00:57:06 +0200 | [diff] [blame] | 117 | + |
Jeff King | 6cf378f | 2012-04-26 04:51:57 -0400 | [diff] [blame] | 118 | When no `<stash>` is given, `stash@{0}` is assumed, otherwise `<stash>` must |
| 119 | be a reference of the form `stash@{<revision>}`. |
SZEDER Gábor | f39d6ee | 2009-06-09 00:57:06 +0200 | [diff] [blame] | 120 | |
Stephen Boyd | fcdd0e9 | 2009-06-17 18:07:37 -0700 | [diff] [blame] | 121 | apply [--index] [-q|--quiet] [<stash>]:: |
SZEDER Gábor | f39d6ee | 2009-06-09 00:57:06 +0200 | [diff] [blame] | 122 | |
Jon Seymour | b0c6bf4 | 2010-08-21 14:09:04 +1000 | [diff] [blame] | 123 | Like `pop`, but do not remove the state from the stash list. Unlike `pop`, |
| 124 | `<stash>` may be any commit that looks like a commit created by |
| 125 | `stash save` or `stash create`. |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 126 | |
Abhijit Menon-Sen | 656b503 | 2008-07-03 11:46:05 +0530 | [diff] [blame] | 127 | branch <branchname> [<stash>]:: |
| 128 | |
| 129 | Creates and checks out a new branch named `<branchname>` starting from |
| 130 | the commit at which the `<stash>` was originally created, applies the |
Jon Seymour | b0c6bf4 | 2010-08-21 14:09:04 +1000 | [diff] [blame] | 131 | changes recorded in `<stash>` to the new working tree and index. |
| 132 | If that succeeds, and `<stash>` is a reference of the form |
| 133 | `stash@{<revision>}`, it then drops the `<stash>`. When no `<stash>` |
Abhijit Menon-Sen | 656b503 | 2008-07-03 11:46:05 +0530 | [diff] [blame] | 134 | is given, applies the latest one. |
| 135 | + |
| 136 | This is useful if the branch on which you ran `git stash save` has |
| 137 | changed enough that `git stash apply` fails due to conflicts. Since |
| 138 | the stash is applied on top of the commit that was HEAD at the time |
| 139 | `git stash` was run, it restores the originally stashed state with |
| 140 | no conflicts. |
| 141 | |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 142 | clear:: |
Junio C Hamano | 9488e87 | 2007-07-01 15:29:01 -0700 | [diff] [blame] | 143 | Remove all the stashed states. Note that those states will then |
Thomas Rast | f5f1e16 | 2009-08-09 02:47:36 +0200 | [diff] [blame] | 144 | be subject to pruning, and may be impossible to recover (see |
| 145 | 'Examples' below for a possible strategy). |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 146 | |
Stephen Boyd | fcdd0e9 | 2009-06-17 18:07:37 -0700 | [diff] [blame] | 147 | drop [-q|--quiet] [<stash>]:: |
Brandon Casey | e25d5f9 | 2008-02-22 13:04:54 -0600 | [diff] [blame] | 148 | |
| 149 | Remove a single stashed state from the stash list. When no `<stash>` |
Jeff King | 6cf378f | 2012-04-26 04:51:57 -0400 | [diff] [blame] | 150 | is given, it removes the latest one. i.e. `stash@{0}`, otherwise |
Sébastien Loriot | 5badfdc | 2012-12-10 08:22:34 +0100 | [diff] [blame] | 151 | `<stash>` must be a valid stash log reference of the form |
Jeff King | 6cf378f | 2012-04-26 04:51:57 -0400 | [diff] [blame] | 152 | `stash@{<revision>}`. |
Brandon Casey | e25d5f9 | 2008-02-22 13:04:54 -0600 | [diff] [blame] | 153 | |
Stephan Beyer | a5ab00c | 2008-08-16 05:27:31 +0200 | [diff] [blame] | 154 | create:: |
| 155 | |
| 156 | Create a stash (which is a regular commit object) and return its |
| 157 | object name, without storing it anywhere in the ref namespace. |
Ramkumar Ramachandra | 2be4351 | 2013-06-15 18:43:22 +0530 | [diff] [blame] | 158 | This is intended to be useful for scripts. It is probably not |
| 159 | the command you want to use; see "save" above. |
Stephan Beyer | a5ab00c | 2008-08-16 05:27:31 +0200 | [diff] [blame] | 160 | |
Ramkumar Ramachandra | bd514ca | 2013-06-15 18:43:25 +0530 | [diff] [blame] | 161 | store:: |
| 162 | |
| 163 | Store a given stash created via 'git stash create' (which is a |
| 164 | dangling merge commit) in the stash ref, updating the stash |
| 165 | reflog. This is intended to be useful for scripts. It is |
| 166 | probably not the command you want to use; see "save" above. |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 167 | |
| 168 | DISCUSSION |
| 169 | ---------- |
| 170 | |
| 171 | A stash is represented as a commit whose tree records the state of the |
| 172 | working directory, and its first parent is the commit at `HEAD` when |
| 173 | the stash was created. The tree of the second parent records the |
| 174 | state of the index when the stash is made, and it is made a child of |
| 175 | the `HEAD` commit. The ancestry graph looks like this: |
| 176 | |
| 177 | .----W |
| 178 | / / |
Junio C Hamano | 114fd81 | 2007-07-04 22:09:20 -0700 | [diff] [blame] | 179 | -----H----I |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 180 | |
| 181 | where `H` is the `HEAD` commit, `I` is a commit that records the state |
| 182 | of the index, and `W` is a commit that records the state of the working |
| 183 | tree. |
| 184 | |
| 185 | |
| 186 | EXAMPLES |
| 187 | -------- |
| 188 | |
| 189 | Pulling into a dirty tree:: |
| 190 | |
| 191 | When you are in the middle of something, you learn that there are |
Junio C Hamano | 9488e87 | 2007-07-01 15:29:01 -0700 | [diff] [blame] | 192 | upstream changes that are possibly relevant to what you are |
| 193 | doing. When your local changes do not conflict with the changes in |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 194 | the upstream, a simple `git pull` will let you move forward. |
| 195 | + |
| 196 | However, there are cases in which your local changes do conflict with |
| 197 | the upstream changes, and `git pull` refuses to overwrite your |
Junio C Hamano | 9488e87 | 2007-07-01 15:29:01 -0700 | [diff] [blame] | 198 | changes. In such a case, you can stash your changes away, |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 199 | perform a pull, and then unstash, like this: |
| 200 | + |
| 201 | ---------------------------------------------------------------- |
| 202 | $ git pull |
SZEDER Gábor | 9da6f0f | 2008-09-02 03:35:24 +0200 | [diff] [blame] | 203 | ... |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 204 | file foobar not up to date, cannot merge. |
| 205 | $ git stash |
| 206 | $ git pull |
Thomas Rast | d183663 | 2009-05-28 11:40:15 +0200 | [diff] [blame] | 207 | $ git stash pop |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 208 | ---------------------------------------------------------------- |
| 209 | |
| 210 | Interrupted workflow:: |
| 211 | |
| 212 | When you are in the middle of something, your boss comes in and |
Junio C Hamano | 9488e87 | 2007-07-01 15:29:01 -0700 | [diff] [blame] | 213 | demands that you fix something immediately. Traditionally, you would |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 214 | make a commit to a temporary branch to store your changes away, and |
Junio C Hamano | 9488e87 | 2007-07-01 15:29:01 -0700 | [diff] [blame] | 215 | return to your original branch to make the emergency fix, like this: |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 216 | + |
| 217 | ---------------------------------------------------------------- |
SZEDER Gábor | 9da6f0f | 2008-09-02 03:35:24 +0200 | [diff] [blame] | 218 | # ... hack hack hack ... |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 219 | $ git checkout -b my_wip |
| 220 | $ git commit -a -m "WIP" |
| 221 | $ git checkout master |
| 222 | $ edit emergency fix |
| 223 | $ git commit -a -m "Fix in a hurry" |
| 224 | $ git checkout my_wip |
| 225 | $ git reset --soft HEAD^ |
SZEDER Gábor | 9da6f0f | 2008-09-02 03:35:24 +0200 | [diff] [blame] | 226 | # ... continue hacking ... |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 227 | ---------------------------------------------------------------- |
| 228 | + |
Thomas Rast | 0b444cd | 2010-01-10 00:33:00 +0100 | [diff] [blame] | 229 | You can use 'git stash' to simplify the above, like this: |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 230 | + |
| 231 | ---------------------------------------------------------------- |
SZEDER Gábor | 9da6f0f | 2008-09-02 03:35:24 +0200 | [diff] [blame] | 232 | # ... hack hack hack ... |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 233 | $ git stash |
| 234 | $ edit emergency fix |
| 235 | $ git commit -a -m "Fix in a hurry" |
Thomas Rast | d183663 | 2009-05-28 11:40:15 +0200 | [diff] [blame] | 236 | $ git stash pop |
SZEDER Gábor | 9da6f0f | 2008-09-02 03:35:24 +0200 | [diff] [blame] | 237 | # ... continue hacking ... |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 238 | ---------------------------------------------------------------- |
| 239 | |
SZEDER Gábor | 7bedebc | 2008-06-27 16:37:15 +0200 | [diff] [blame] | 240 | Testing partial commits:: |
| 241 | |
| 242 | You can use `git stash save --keep-index` when you want to make two or |
| 243 | more commits out of the changes in the work tree, and you want to test |
| 244 | each change before committing: |
| 245 | + |
| 246 | ---------------------------------------------------------------- |
SZEDER Gábor | 9da6f0f | 2008-09-02 03:35:24 +0200 | [diff] [blame] | 247 | # ... hack hack hack ... |
Eric Raible | caf1899 | 2008-07-08 00:40:56 -0700 | [diff] [blame] | 248 | $ git add --patch foo # add just first part to the index |
| 249 | $ git stash save --keep-index # save all other changes to the stash |
| 250 | $ edit/build/test first part |
SZEDER Gábor | f733c70 | 2008-09-02 03:45:01 +0200 | [diff] [blame] | 251 | $ git commit -m 'First part' # commit fully tested change |
Eric Raible | caf1899 | 2008-07-08 00:40:56 -0700 | [diff] [blame] | 252 | $ git stash pop # prepare to work on all other changes |
SZEDER Gábor | 9da6f0f | 2008-09-02 03:35:24 +0200 | [diff] [blame] | 253 | # ... repeat above five steps until one commit remains ... |
Eric Raible | caf1899 | 2008-07-08 00:40:56 -0700 | [diff] [blame] | 254 | $ edit/build/test remaining parts |
| 255 | $ git commit foo -m 'Remaining parts' |
SZEDER Gábor | 7bedebc | 2008-06-27 16:37:15 +0200 | [diff] [blame] | 256 | ---------------------------------------------------------------- |
| 257 | |
Thomas Rast | f5f1e16 | 2009-08-09 02:47:36 +0200 | [diff] [blame] | 258 | Recovering stashes that were cleared/dropped erroneously:: |
| 259 | |
| 260 | If you mistakenly drop or clear stashes, they cannot be recovered |
| 261 | through the normal safety mechanisms. However, you can try the |
| 262 | following incantation to get a list of stashes that are still in your |
| 263 | repository, but not reachable any more: |
| 264 | + |
| 265 | ---------------------------------------------------------------- |
| 266 | git fsck --unreachable | |
| 267 | grep commit | cut -d\ -f3 | |
| 268 | xargs git log --merges --no-walk --grep=WIP |
| 269 | ---------------------------------------------------------------- |
| 270 | |
| 271 | |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 272 | SEE ALSO |
| 273 | -------- |
Dan McGee | 5162e69 | 2007-12-29 00:20:38 -0600 | [diff] [blame] | 274 | linkgit:git-checkout[1], |
| 275 | linkgit:git-commit[1], |
| 276 | linkgit:git-reflog[1], |
| 277 | linkgit:git-reset[1] |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 278 | |
しらいしななこ | 09ccdb6 | 2007-07-01 14:26:08 +0900 | [diff] [blame] | 279 | GIT |
| 280 | --- |
Christian Couder | 9e1f0a8 | 2008-06-06 09:07:32 +0200 | [diff] [blame] | 281 | Part of the linkgit:git[1] suite |