From: "David Kågedal" <davidk@lysator.liu.se>
To: git@vger.kernel.org
Subject: Re: Importing from CVS issues
Date: Tue, 16 Aug 2005 14:16:15 +0200 [thread overview]
Message-ID: <u5toe7y2i28.fsf@fidgit.hq.vtech> (raw)
In-Reply-To: 1124188894.7444.9.camel@okra.transitives.com
Alex Bennee <kernel-hacker@bennee.com> writes:
> Before the import script finally dies with:
>
> WARNING: revision 1.3.2.1 of file
> scripts/xmltools/t/data/gzip/DO-NOT-BACKUP on unnamed branch
> DONE; creating master branch
> cp: cannot stat `/export/test/cvstogit/.git/refs/heads/origin': No such
> file or directory
Was this done with an empty destination dir? I've seen similar things
happen in a dir where an interrupted cvs import was done previously,
and the 'origin' branch was never created.
--
David Kågedal
next prev parent reply other threads:[~2005-08-16 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 10:41 Importing from CVS issues Alex Bennee
2005-08-16 11:26 ` Martin Langhoff
2005-08-16 16:09 ` Alex Bennee
2005-08-16 12:16 ` David Kågedal [this message]
2005-08-16 13:48 ` Alex Bennee
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=u5toe7y2i28.fsf@fidgit.hq.vtech \
--to=davidk@lysator.liu.se \
--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).