Re: Bug in cperl-mode.el - unexpanded CVS keyword
>>>> Stephen J Turnbull <stephen(a)xemacs.org> writes:
Because it defaults to automatic expansion, we never notice unless
upstream complains that we've checked into our CVS and they're
getting uninterpretable bug reports with our version numbers, not
theirs.
If our version is just a sync I think the version number should be the
same as upstream. The version number could be used out there to
identify the package version so if we change that into our version
strange things could happen. So the automatic expansion is not our
friend in this case.
The problem when you switch to a different VCS is that the format of
expanded keywords changes, breaking regexps etc used to capture the
version number. You'll typically get the same kind of bug that Vin
observed.
It seems like the Revision mostly is used as a convenient way to get a
standard numeric version number so that checking in a specific file
bumps the version. So the version numbers in Mercurial et al is not
useful here and other solutions are needed.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta