From: Kalle Valo <Kalle.Valo@iki.fi>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: cvsimport error: need a valid pathname
Date: Sat, 27 Aug 2005 20:44:33 +0300 [thread overview]
Message-ID: <87zmr39svy.fsf@litku.valo.iki.fi> (raw)
In-Reply-To: <46a038f905082708371719121c@mail.gmail.com> (Martin Langhoff's message of "Sun, 28 Aug 2005 03:37:48 +1200")
Martin Langhoff <martin.langhoff@gmail.com> writes:
> On 8/28/05, Kalle Valo <Kalle.Valo@iki.fi> wrote:
>> The documentation says that it should be possible to update
>> incrementally from the CVS repository. Am I doing something wrong or
>> is this a bug?
>
> It _should_ work the way you are running it, so consider it a bug. Do
> you think you can do some tinkering/debugging to tell us some more?
I investigated it and realized that this was my mistake. I had copied
the imported git repository from my laptop to my desktop using 'scp
-r' and it changed .git/HEAD to a file, not a link as it should have
been. I copied it again, this time with tar to preserve symbolic
links, and cvsimport started to work again. So this was just a PEBCAK.
Thanks for your help.
> Otherwise. how large is the cvs repo?
'git log | grep commit | wc -l' says 2704 commits. I have to say that
git has made my life a lot easier. It was really easy to import the
CVS history to git and now I can read the history properly with gitk.
With CVS I would have been banging my head to the wall all the time.
Now all I want is svnimport and darcsimport :)
--
Kalle Valo
next prev parent reply other threads:[~2005-08-27 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-27 14:48 cvsimport error: need a valid pathname Kalle Valo
2005-08-27 15:37 ` Martin Langhoff
2005-08-27 17:44 ` Kalle Valo [this message]
2005-08-27 20:54 ` Make .git directory validation code test HEAD Linus Torvalds
2005-08-28 4:56 ` 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=87zmr39svy.fsf@litku.valo.iki.fi \
--to=kalle.valo@iki.fi \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.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).