Are my RCS files actually malformed?

[Peter Budny]

Hello,

 

I’m trying to run cvs2hg on a very old CVS repository. This repository has gone through at least one other conversion tool (mks2cvs) about 10 years ago, has had heavy use with CVSNT… the usual things that will probably make you groan.

 

Anyway, the tool keeps complaining about malformed RCS edits, and I can’t find enough documentation on what constitutes a *well-formed* RCS edit to figure out whether it’s the RCS file at fault or the tool. I’m hoping you can answer a couple of examples for me, and then I’ll know whether I should try to fix the file or the tool.

 

Case 1:

If you have a file that ends with a Unix newline (‘\n’), how many lines does it have?

In other words, should an edit for that file look like:

@d1 50

a50 1

This file ends with a newline character.

@

Or should it look like:

@d1 50

a50 2

This file ends with a newline character.

@

Does it matter if the file is binary?

I assume that if the file *doesn’t* end in a newline, then it only has 1 line, such as:

@d1 50

a50 1

This file ends right here.@

 

Case 2:

Does it matter if the “text” command after the log is on a new line? Or can it follow the “@” ending the log immediately without a newline?

In other words, is this a valid revision?

1.5

log

@ @text

@@

 

I may have more questions, but if you can answer these, or show me where to find decent documentation of the format (the best I found was on the Info page for Diffutils, but that doesn’t answer either of these questions), I’d be really grateful.

 

--

Peter Budny

Unicoi Systems