git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 27, 2008, 20:18 UTC
Message-ID
<7vtzhnf3w5.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20080427173731.GA9523@cuci.nl>
"Stephen R. van den Berg" <srb@cuci.nl> writes:
Show 13 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.  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?

Previous: Stephen R. van den BergNext: Stephen R. van den Berg
Message 8 of 10 in “How to fetch missing pack”
  1. Jörg SommerApr 12, 2008
  2. Peter BaumannApr 13, 2008
  3. Jörg SommerApr 23, 2008
  4. Christian CouderApr 24, 2008
  5. Shawn O. PearceApr 24, 2008
  6. git doesn't finds the parent of a commit (was: How to fetch missing pack)Jörg Sommer, Apr 27, 2008
  7. Stephen R. van den BergApr 27, 2008
  8. Junio C HamanoApr 27, 2008
  9. Stephen R. van den BergApr 27, 2008
  10. Jörg SommerApr 28, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.