reaction is to regretfully point out that the comma-v syntax is frozen As someone who still uses RCS daily on multiple machines, and is highly concerned about compatibility, I can still say that this particular change seems unproblematic to me. If I'm understanding it right.
If a ,v file has extra information, and GNU RCS simply preserves it, that's not going to hurt any existing use of RCS -- no one else would even know about it. Likewise, if GNU RCS adds new information to a ,v given some new option or whatever, that's also not going to hurt any existing use, because it's explicitly asked for. The problem would be with any existing ,v files getting munged in some way merely when a new version of RCS does a normal operation. As I recall, the previous discussion was along those lines. FWIW ... karl
