author | Thomas Rast <trast@student.ethz.ch> | |
Sun, 9 Aug 2009 00:47:36 +0000 (02:47 +0200) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Mon, 10 Aug 2009 01:33:41 +0000 (18:33 -0700) | ||
commit | f5f1e164bd4234683e5a1fc4a49a77b1b01855f8 | |
tree | 4dc6332a21b1d3f3edde0d3cf7dc417cd8c6ad47 | tree | snapshot |
parent | c14417c4f5f8d7765e232f1e908b85d2ae14ec34 | commit | diff |
Document 'stash clear' recovery via unreachable commits
Add an example to the stash documentation that shows how to quickly
find candidate commits among the 'git fsck --unreachable' output.
Unless you have merges of branch names containing WIP, or edit your
merge messages to say WIP, there will be no false positives.
Snippet written by Björn "doener" Steinbrink and me after zepolen_
asked on IRC.
Signed-off-by: Thomas Rast <trast@student.ethz.ch>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Add an example to the stash documentation that shows how to quickly
find candidate commits among the 'git fsck --unreachable' output.
Unless you have merges of branch names containing WIP, or edit your
merge messages to say WIP, there will be no false positives.
Snippet written by Björn "doener" Steinbrink and me after zepolen_
asked on IRC.
Signed-off-by: Thomas Rast <trast@student.ethz.ch>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/git-stash.txt | diff | blob | history |