git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Jeff King" <peff@peff.net>
Cc: "Miklos Vajna" <vmiklos@frugalware.org>,
	git@vger.kernel.org, "Stefan Sperling" <stsp@stsp.name>
Subject: Re: cvsimport: trying to convert freebsd cvs to git
Date: Mon, 24 Dec 2007 10:13:34 +1300	[thread overview]
Message-ID: <46a038f90712231313k3d17a30bwa910dd9679851c92@mail.gmail.com> (raw)
In-Reply-To: <20071223172913.GA9297@sigill.intra.peff.net>

On Dec 24, 2007 6:29 AM, Jeff King <peff@peff.net> wrote:
> On Sat, Dec 22, 2007 at 06:18:01PM +0100, Miklos Vajna wrote:
>
> > then i tried:
> >
> > $ time git cvsimport -d `pwd`/cvs -C src.git src
> > Initialized empty Git repository in /home/vmiklos/git/freebsd/src.git/.git/
> > malformed revision
>
> This is the actual error; everything else is git-cvsimport failing to
> notice the problem and continuing anyway.
>
> I will take a look and see if it is simple to stop the process here and
> produce a better error message.

Indeed. Running verbose will name the branch name that triggers that
error. One thing I find useful is to capture the commandline passed to
cvsps (using ps), stopping cvsimport+cvsps, and running cvsps by hand
with the same commandline (remember to set TZ=UTC in the
environment!), saving STDOUT to a file.

Once you have the file, you can feed it to cvsimport with the -P
parameter (IIRC). Usually cvsimport errors are all about wonky cvsps
output.

For the record, I normally do my initial imports with Keith's
parsecvs, and then run incrementals using git-cvsimport. These
incrementals aren't 100% perfect, so I routinely check for 'drift'.

cheers,


m

  reply	other threads:[~2007-12-23 21:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-22 17:18 cvsimport: trying to convert freebsd cvs to git Miklos Vajna
2007-12-23  1:47 ` Anand Kumria
2007-12-23 12:06   ` David Soria Parra
2007-12-23 17:29 ` Jeff King
2007-12-23 21:13   ` Martin Langhoff [this message]
2007-12-24  3:05 ` Jeff King
2007-12-24  3:08   ` [PATCH] cvsimport: die on cvsps errors Jeff King
2007-12-24  3:21     ` Martin Langhoff
2007-12-24 12:43     ` Miklos Vajna

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=46a038f90712231313k3d17a30bwa910dd9679851c92@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=stsp@stsp.name \
    --cc=vmiklos@frugalware.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).