From: Junio C Hamano <gitster@pobox.com>
To: Thomas Glanzmann <thomas@glanzmann.de>
Cc: GIT <git@vger.kernel.org>
Subject: Re: fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Date: Fri, 08 Jun 2007 03:27:30 -0700 [thread overview]
Message-ID: <7vk5uekagd.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7vodjqkazp.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Fri, 08 Jun 2007 03:15:54 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Perhaps repository was set up in an unusual way by hand
> (i.e. not by a clone), such that:
>
> 1. you have HEAD pointing at a branch (e.g. 'refs/heads/master'),
> 2. which does _not_ exist yet (i.e. no 'refs/heads/master'),
> 3. yet you have a tag that you can try to detach your HEAD to (e.g. v2.6.20).
>
> ... well that was my initial guess, but even after setting up such a
> funny repository by hand, I cannot seem to reproduce it.
Actually, that turns out to be the reason for 'maint' releases,
although it works on 'master' (hence will be in 1.5.3 later).
How did you get your repository into such a state to begin with?
next prev parent reply other threads:[~2007-06-08 10:27 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
2007-06-08 10:33 ` Junio C Hamano
2007-06-08 10:38 ` Thomas Glanzmann
2007-06-08 10:27 ` Junio C Hamano [this message]
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=7vk5uekagd.fsf@assigned-by-dhcp.cox.net \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=thomas@glanzmann.de \
/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).