From: Junio C Hamano <gitster@pobox.com>
To: Thomas Rast <trast@student.ethz.ch>
Cc: git@vger.kernel.org, "Björn Steinbrink" <B.Steinbrink@gmx.de>
Subject: Re: [PATCH] Document 'stash clear' recovery via unreachable commits
Date: Sat, 08 Aug 2009 18:25:55 -0700 [thread overview]
Message-ID: <7veirlbwws.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <9e8ddf7c6c4d4df4150bff0467b461bfff92a401.1249778711.git.trast@student.ethz.ch> (Thomas Rast's message of "Sun\, 9 Aug 2009 02\:47\:36 +0200")
Thomas Rast <trast@student.ethz.ch> writes:
> Add an example to the stash documentation that shows how to quickly
> find candidate commits among the 'git fsck --unreachable' output.
Thanks.
> Unless you have merges of branch names containing WIP, or edit your
> merge messages to say WIP, there will be no false positives.
That may be true, but I suspect that people's stash entries that are worth
saving are given their own messages with "git stash save 'message'" and do
not necessarily say WIP. I wish if there were a better way to identify
them, but I do not think of any offhand.
next prev parent reply other threads:[~2009-08-09 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-09 0:47 [PATCH] Document 'stash clear' recovery via unreachable commits Thomas Rast
2009-08-09 1:25 ` Junio C Hamano [this message]
2009-08-09 2:21 ` Björn Steinbrink
2009-08-09 9:26 ` Sitaram Chamarty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7veirlbwws.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=B.Steinbrink@gmx.de \
--cc=git@vger.kernel.org \
--cc=trast@student.ethz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).