Re: git doesn't finds the parent of a commit

From: Jörg Sommer <joerg@alea.gnuu.de>
Date: Apr 28, 2008, 14:14 UTC
Message-ID: <slrng1bmua.25r.joerg@alea.gnuu.de>
In-Reply-To: <20080427173731.GA9523@cuci.nl>

Hallo,

"Stephen R. van den Berg" <srb@cuci.nl> wrote:

Show 10 quoted lines

> J?rg Sommer wrote:
>>% git rev-parse b63e99500137c913bd801a2f22b6cf88c63b95c5~1
>>b63e99500137c913bd801a2f22b6cf88c63b95c5~1
>>fatal: ambiguous argument 'b63e99500137c913bd801a2f22b6cf88c63b95c5~1': unknown revision or path not in the working tree.
>>Use '--' to separate paths from revisions
>
>>Can someone tell me what I'm doing wrong?
>
> I've had similar symptoms when I had circular references in the
> repository.

No, this was not my problem. But I found the reason with bisect: .git/shallow. I've started with a shallow clone, but forgot it. Is it possible that git warns about this or ignores the shallow entry if the parent of the commit is available?

Bye, Jörg.

-- 
Dein Gesicht wird dir geschenkt. Lächeln musst du selber! (Inga Hermann)