Re: RCS files with extension can no longer be read

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

() Vincent Lefevre <[email protected]>
() Mon, 5 Jun 2017 11:19:13 +0200

   On 2017-06-04 05:57:44 +0200, Thien-Thi Nguyen wrote:
   > As you might know, the RCS 5.8 (2011-08-30) NEWS mentions:
   >=20
   >  - RCS file top-level grammar frozen.
   [...]

   Thanks for the details. When I searched for the meaning of the error
   message, I just found: https://savannah.gnu.org/bugs/?35149 where it
   it is said that the grammar was frozen, but with no details.

   > I suppose the middle way would be to add back support for
   > "newphrases", in read-only mode (not passthrough).  However, i
   > am loathe to do that and would rather improve the documentation
   > (by writing it, first, and iterating, subsequently) on how to
   > batch-convert ,v files to embed their extra metainfo in the
   > =E2=80=98integrity=E2=80=99 field.

   I think that such documentation may indeed be a better solution.

   Moreover, the error message should be more informative, allowing the
   user to easily find the cause of the problem and how to avoid it.

Documentation is the bane/solution of all software problems, it
seems.  :-D

=2D-=20
Thien-Thi Nguyen

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iG4EARECAC4WIQR0jqDoHLinSJv6bORnAyIkTIB1AgUCX3tjXxAcdHRuQGdudXZv
bGEub3JnAAoJEGcDIiRMgHUC/K0AoNJhL/Wt9ossZkitn+UA63JgecVZAKDBJZHa
TZlu8k2m4v3pME98Ei0qUQ==
=ugNs
-----END PGP SIGNATURE-----
--=-=-=--