git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Karlsson <peter@softwolves.pp.se>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: PVCS (or RCS) importer for Git?
Date: Mon, 31 Mar 2008 07:26:10 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0803310723440.26808@ds9.cixit.se> (raw)
In-Reply-To: <alpine.LSU.1.00.0803281730060.18259@racer.site>

Johannes Schindelin:

> I once tried, but apparently, there are different repository formats
> for PVCS. For example, pvcs2cvs did not work for me.

Yeah, the format is binary. That is why I am trying to use the
command-line tools.

> IIRC I used a simple shell script to convert pvcs (using the
> mega-slow command line tools) to ,v files.  Then I converted that to Git.

That is, more or less, what the pvcs2cvs script does. I've had some
success with it.

> Judging from the problems of importing CVS to Git (which mostly stem
> from the file-versioning paradigm), I suggest not trying to be too
> clever, but convert it to cvs and use a good cvs importer, such as
> cvs2svn (which despite its name also imports into Git) or parsecvs.

Given that the PVCS history file ("trail") that I was trying to follow
didn't quite work out, because there had been some direct manipulations
of the PVCS repository that were not recorded there, I think that is
the way I will have to go. That means I do lose the tagging
information (timestamp and tagger), but I can live with that...

Thanks for the input.
-- 
\\// Peter - http://www.softwolves.pp.se/

      reply	other threads:[~2008-03-31  6:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 16:17 PVCS (or RCS) importer for Git? Peter Karlsson
2008-03-28 16:33 ` Johannes Schindelin
2008-03-31  6:26   ` Peter Karlsson [this message]

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.0803310723440.26808@ds9.cixit.se \
    --to=peter@softwolves.pp.se \
    --cc=Johannes.Schindelin@gmx.de \
    --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).