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/
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
