From: Thomas Glanzmann <thomas@glanzmann.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: GIT <git@vger.kernel.org>
Subject: Re: fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Date: Fri, 8 Jun 2007 12:21:13 +0200 [thread overview]
Message-ID: <20070608102113.GB2335@cip.informatik.uni-erlangen.de> (raw)
In-Reply-To: <7vodjqkazp.fsf@assigned-by-dhcp.cox.net>
Hello Junio,
> ... well that was my initial guess, but even after setting up such a
> funny repository by hand, I cannot seem to reproduce it.
This was on a fresh clone. What I did was:
(s017241) [/usr/src] git clone 131.188.30.102:/scratch/tg/linux-2.6/
Initialized empty Git repository in /usr/src/linux-2.6/.git/
remote: Generating pack...
remote: Done counting 496189 objects.
remote: Deltifying 496189 objects...
remote: 100% (496189/496189) done
Indexing 496189 objects...
remote: Total 496189 (delta 401610), reused 496189 (delta 401610)
100% (496189/496189) done
Resolving 401610 deltas...
100% (401610/401610) donedone
fatal: Not a valid object name HEAD
I see it. Last line. I tried to clone from a repository which itself had a
detached HEAD. Could that be the problem?
Thomas
next prev parent reply other threads:[~2007-06-08 10:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 10:08 fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree Thomas Glanzmann
2007-06-08 10:15 ` Junio C Hamano
2007-06-08 10:21 ` Thomas Glanzmann [this message]
2007-06-08 10:33 ` Junio C Hamano
2007-06-08 10:38 ` Thomas Glanzmann
2007-06-08 10:27 ` Junio C Hamano
2007-06-10 8:54 ` carbonated beverage
-- strict thread matches above, loose matches on Subject: below --
2010-10-28 13:09 fatal: ambiguous argument 'HEAD^': " Todd Wells
2010-10-28 13:41 ` SZEDER Gábor
2010-10-28 13:42 ` Mathias Lafeldt
2010-10-28 13:42 ` Santi Béjar
[not found] ` <AANLkTi=QODz+Gf9hwrdu6b900CzuO-BBnF2zmLWOGFpy@mail.gmail.com>
2010-10-28 14:01 ` Santi Béjar
2015-09-09 8:34 ` davilda_
2015-09-09 9:20 ` Jeff King
2015-09-09 16:24 ` Junio C Hamano
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=20070608102113.GB2335@cip.informatik.uni-erlangen.de \
--to=thomas@glanzmann.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).