Re: cannot find hash in the log output

From: Jeff King <peff@peff.net>
Date: Dec 3, 2010, 17:52 UTC
Message-ID: <20101203175212.GA8267@sigill.intra.peff.net>
In-Reply-To: <AANLkTinAUfFge-AcfQevG2_9Gi3oOPy+-SrEZrfp4byn@mail.gmail.com>

On Fri, Dec 03, 2010 at 12:41:52PM -0500, Eugene Sajine wrote:

Show 13 quoted lines

> > yes. I do see it with your command.
> >
> > git ls-tree -r HEAD | grep <resulting SHA1 from git hash-object>
> >
> > Thanks,
> > Eugene
> >
> 
> While I'm able to see that object using the command Junio has provided
> the question remains the same:
> How could the file get into the state where its hash (git has-object
> file-name) cannot be found in any commit (git log --raw --no-abbrev |
> grep SHA1), if there was no local changes made to the file???

If the blob was created as the resolution of a merge conflict, I don't think that will appear in the output of "git log --raw".

-Peff