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