Re: (LONG-ish) Bringing cvsnt mergepoint processing into CVS: req uest for feedback

[Derek Robert Price]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jim.Hyslop wrote:

>Mark D. Baushke wrote:
>
>>A question... I seem to recall that CvsNT records a new 'mergepoint'
>>keyword into the RCS format and that such ,v files thereafter had
>>problems with normal RCS command operating on them (although
>>it may have
>>been the 'commitid: <hashvalue>;' that was the real culprit
>>when I last
>>looked. Could you answer if you are adding a new keyword to the RCS
>>structure or not?
>
>Corollary question - does this mean that RCS does not like keywords that it
>doesn't understand in the file?
>
>Just out of curiosity, does anyone still use RCS?


- From CVS's doc/RCSFILES:

> The RCS file format allows quite a variety of extensions to be added
> in a compatible manner by use of the "newphrase" feature documented in
> rcsfile.5.  We won't try to document extensions not used by CVS in any
> detail, but we will briefly list them.  Each occurrence of a newphrase
> begins with an identifier, which is what we list here.  Future
> designers of extensions are strongly encouraged to pick
> non-conflicting identifiers.  Note that newphrase occurs several
> places in the RCS grammar, and a given extension may not be legal in
> all locations.  However, it seems better to reserve a particular
> identifier for all locations, to avoid confusion and complicated
> rules.


and so on.  I'm not sure how easy it is or what the rcsfiles.5 man page
has to say, but the implication does appear to be that there is a way to
extend RCS in a backwards-compatible way.

Derek

- --
                *8^)

Email: derek@ximbiot.com

Get CVS support at <http://ximbiot.com>!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org

iD8DBQFAM8wILD1OTBfyMaQRAgi+AJ4lE0idpWJNKFySQiPySzpG5q/wAwCfS0dy
+AqqvBK0ZT1/rV0piwUB/TM=
=ZPej
-----END PGP SIGNATURE-----