"Stephen R. van den Berg" <srb@xxxxxxx> writes: > 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. They're not reported by any of the existing checks, I've > submitted a patch (resent it just now) which causes git to check for > (and report) circular references when using --topo-order on e.g. > git-rev-list. Assuming that we never have SHA-1 hash collisions, the graft mechansim is practically the only way to get yourself into the circular reference situation. Perhaps we should check this circularity when we install grafts instead of special casing the topo-order codepath? How expensive would that alternative approach be? -- 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
