git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Grzegorz Kulewski <kangur@polcom.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git-cvsimport problem
Date: Mon, 29 May 2006 21:37:17 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0605292122580.5623@g5.osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0605300236270.25988@alpha.polcom.net>



On Tue, 30 May 2006, Grzegorz Kulewski wrote:
> 
> and it looks like it hangs in the middle with message:
> 
> cvs [rlog aborted]: unexpected '\x0' reading revision number in RCS file
> /home/cvsroot/lms/templates/noaccess.html,v

Are you sure that CVS archive isn't corrupted? That sounds like an 
internal CVS error to me. Doing a "git cvsimport" will obviously get every 
single version of every single file, so it will inevitably also hit errors 
that you migt not hit with a regular "cvs co" (which will only get the 
current version).

There's bound to be some "fsck for CVS" (since people edit files by hand, 
and mistakes must happen), but I have no idea.

That said, it's not like we haven't had our share of cvsps issues and 
other things, so who knows..

> and to my understanding does not do anything usefull next. Nothing is imported
> (there is only nearly empty .git tree).

Do "git log origin" to see what has been imported. If a cvsimport is 
broken in the middle, you'll not get any checked-out state, and your HEAD 
won't point to anything, but the "origin" branch has been created and 
contains whatever has been imported so far.

			Linus

  parent reply	other threads:[~2006-05-30  4:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-30  1:06 git-cvsimport problem Grzegorz Kulewski
2006-05-30  1:56 ` Martin Langhoff
2006-05-30  4:37 ` Linus Torvalds [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-30  5:55 Alenoosh Baghumian
2008-04-30 10:12 ` Michael Haggerty
2008-05-07 11:30 Alenoosh Baghumian
2008-05-28 12:15 ` Madhu

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=Pine.LNX.4.64.0605292122580.5623@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=git@vger.kernel.org \
    --cc=kangur@polcom.net \
    /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).