From: Anand Kumria <wildfire@progsoc.org>
To: git@vger.kernel.org
Subject: Re: Commits gone AWOL, but not reported by git-fsck --unreachable
Date: Sat, 19 May 2007 15:45:49 +0000 (UTC) [thread overview]
Message-ID: <pan.2007.05.19.15.45.46@progsoc.org> (raw)
In-Reply-To: 20070519121154.GA10268@coredump.intra.peff.net
On Sat, 19 May 2007 08:11:54 -0400, Jeff King wrote:
> On Sat, May 19, 2007 at 05:09:33AM -0700, Robin H. Johnson wrote:
>
>> Ahh, they do show up there (and I learnt a new git command now, thanks)
>> - the ones that I can remember the Subject lines for anyway.
>>
>> Any hints for the future on finding stuff that is in the reflog but not
>> in the tree? (Remembering every subject line isn't feasible).
>
> Try 'git-fsck --unreachable --no-reflogs'. :)
What version? git 1.5.1.4 doesn't seem to have that.
Anand
next prev parent reply other threads:[~2007-05-19 15:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 10:30 Commits gone AWOL, but not reported by git-fsck --unreachable Robin H. Johnson
2007-05-19 11:52 ` Jeff King
2007-05-19 12:09 ` Robin H. Johnson
2007-05-19 12:11 ` Jeff King
2007-05-19 15:45 ` Anand Kumria [this message]
2007-05-19 16:08 ` Matthieu Moy
2007-05-19 16:20 ` Brian Gernhardt
2007-05-19 16:55 ` Matthieu Moy
2007-05-19 17:13 ` Brian Gernhardt
2007-05-19 18:15 ` Junio C Hamano
2007-05-20 12:37 ` [PATCH] Cross-reference the manpages for git-name-rev and git-describe (was Re: Commits gone AWOL, but not reported by git-fsck --unreachable) Matthieu Moy
[not found] ` <7vsl9rmkm0.fsf@assigned-by-dhcp.cox.net>
2007-05-21 7:20 ` [PATCH] Cross-reference the manpages for git-name-rev and git-describe Shawn O. Pearce
2007-05-21 7:46 ` Junio C Hamano
2007-05-21 7:54 ` Shawn O. Pearce
2007-05-21 8:01 ` Matthieu Moy
2007-05-22 6:13 ` Junio C Hamano
2007-05-22 6:17 ` Shawn O. Pearce
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=pan.2007.05.19.15.45.46@progsoc.org \
--to=wildfire@progsoc.org \
--cc=git@vger.kernel.org \
/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).