git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen R. van den Berg" <srb@cuci.nl>
To: git@vger.kernel.org
Subject: Re: git doesn't finds the parent of a commit (was: How to fetch missing pack)
Date: Sun, 27 Apr 2008 19:37:31 +0200	[thread overview]
Message-ID: <20080427173731.GA9523@cuci.nl> (raw)
In-Reply-To: <20080427104704.GA11784@alea.gnuu.de>

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.
-- 
Sincerely,                                                          srb@cuci.nl
           Stephen R. van den Berg.

  reply	other threads:[~2008-04-27 17:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-12 12:07 How to fetch missing pack Jörg Sommer
2008-04-13  9:41 ` Peter Baumann
2008-04-23 20:55   ` Jörg Sommer
2008-04-24  6:01     ` Christian Couder
2008-04-24  6:08       ` Shawn O. Pearce
2008-04-27 10:47         ` git doesn't finds the parent of a commit (was: How to fetch missing pack) Jörg Sommer
2008-04-27 17:37           ` Stephen R. van den Berg [this message]
2008-04-27 20:18             ` git doesn't finds the parent of a commit Junio C Hamano
2008-04-27 21:46               ` Stephen R. van den Berg
2008-04-28 14:14             ` Jörg Sommer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080427173731.GA9523@cuci.nl \
    --to=srb@cuci.nl \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).