| OLD | NEW |
| (Empty) |
| 1 git-freeze(1) | |
| 2 ============= | |
| 3 | |
| 4 NAME | |
| 5 ---- | |
| 6 git-freeze - | |
| 7 include::_git-freeze_desc.helper.txt[] | |
| 8 | |
| 9 SYNOPSIS | |
| 10 -------- | |
| 11 [verse] | |
| 12 'git freeze' | |
| 13 | |
| 14 DESCRIPTION | |
| 15 ----------- | |
| 16 | |
| 17 `git freeze` works a lot like `git stash`, in that it stores the current changes | |
| 18 in your working copy and index 'somewhere'. Unlike `git stash`, `git freeze` | |
| 19 stores those changes on your current branch. This effectively allows you to | |
| 20 'pause' development of a branch, work on something else, and then come back to | |
| 21 exactly the same working state later (by running `git thaw`). | |
| 22 | |
| 23 `git freeze` will make up to 2 commits on your branch. A commit with the message | |
| 24 `FREEZE.indexed` will contain all changes which you’ve added to your index (like | |
| 25 with 'git add', 'git mv', 'git rm', etc.). A commit with the message | |
| 26 `FREEZE.unindexed` will contain all changes which were not in your index at the | |
| 27 time you ran git freeze (freshly modified files, new files, etc.). | |
| 28 | |
| 29 EXAMPLE | |
| 30 ------- | |
| 31 demo:1[] | |
| 32 | |
| 33 SEE ALSO | |
| 34 -------- | |
| 35 linkgit:git-thaw[1] | |
| 36 | |
| 37 include::_footer.txt[] | |
| 38 | |
| 39 // vim: ft=asciidoc: | |
| OLD | NEW |