Updating CVS repo to UseNewInfoFmtStrings=yes

[Barry Hawkins]

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

Barry Hawkins wrote:
[...]
> Of course, now I haven't gotten any mail for my test commits, and after
> three silent test commits, the original warning reappeared on the fourth
> one.  So, if anyone has some insight on what might be wrong, I'd love to
> know.  We are still able to use CVS, we just seem to still get the
> annoying warnings and not receive commit mails.  I'll keep looking into
> the issue.
[...]
OK, didn't want to go to bed without the emails working.  Reverted to
the original cvs-mailcommit script (always wanted a reason to do a
reversion in CVS; it was kind of anti-climactic) and the old --cvs
syntax with the '1' compatibility fix.  Now you get alternation between
the slightly less verbose message and the full one on commit and mail is
working again, which is unsettling to me, since the configuration isn't
being updated.  I'll keep looking into what the issue is with the new
syntax not working; the same version of the script is in stable,
testing, and unstable, so it should work as the man page says.

Regards,
- --
Barry Hawkins
site: www.bytemason.org
weblog: www.yepthatsme.com

Registered Linux User #368650
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDF+9XHuKcDICy0QoRAmDvAKD0NtHUJjzc3XS96azvTvdsNBJsuQCfeuJT
4UTDs+574zo+KKFm1FVPhNg=
=0/HE
-----END PGP SIGNATURE-----