Re: Commits gone AWOL, but not reported by git-fsck --unreachable

Anand Kumria [off-list ref] writes:

On Sat, 19 May 2007 08:11:54 -0400, Jeff King wrote:

quoted

On Sat, May 19, 2007 at 05:09:33AM -0700, Robin H. Johnson wrote:

quoted

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.

The commit introducing it is 566842f62bdf1f16c2e94fb431445d2e6c0f3f0b,
and I'd say it's in git 1.5.1:

$ git-describe --tags 566842f62bdf1f16c2e94fb431445d2e6c0f3f0b                                                                                     
v1.5.1-34-g566842f

-- 
Matthieu

On May 19, 2007, at 12:08 PM, Matthieu Moy wrote:

The commit introducing it is 566842f62bdf1f16c2e94fb431445d2e6c0f3f0b,
and I'd say it's in git 1.5.1:

$ git-describe --tags 566842f62bdf1f16c2e94fb431445d2e6c0f3f0b
v1.5.1-34-g566842f

Actually, I think that means it's 34 commits *after* v1.5.1, not  
before.  It's in 1.5.2-rc0, but none of the 1.5.1.* series.

~~ Brian