Hallo, "Stephen R. van den Berg" <srb@xxxxxxx> wrote: > 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) -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
