From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "carbonated beverage" <ramune@net-ronin.org>
Cc: git@vger.kernel.org
Subject: Re: cvs import error
Date: Mon, 12 Jun 2006 12:31:35 +1200 [thread overview]
Message-ID: <46a038f90606111731q34fe431fn36d751b387ab69a9@mail.gmail.com> (raw)
In-Reply-To: <20060611234842.GA12713@prophet.net-ronin.org>
On 6/12/06, carbonated beverage <ramune@net-ronin.org> wrote:
> fatal: Not a valid object name HEAD
> checkout failed: 256
> $ exit
After each attempt, the import leaves a .git file around. rm -fr .git
before retrying... or just retry in a new directory every time ;-)
(... we should die with a more helpful message here...)
cheers,
martin
next prev parent reply other threads:[~2006-06-12 0:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-11 23:48 cvs import error carbonated beverage
2006-06-12 0:31 ` Martin Langhoff [this message]
2006-06-12 3:57 ` carbonated beverage
2006-06-12 4:01 ` Martin Langhoff
2006-06-13 4:25 ` carbonated beverage
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=46a038f90606111731q34fe431fn36d751b387ab69a9@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=ramune@net-ronin.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).