Re: RCS keyword removal

[Miles Bader <miles@lsi.nec.co.jp>]

Andre Spiegel <spiegel@gnu.org> writes:
> A general approach might be to switch off keyword expansion for
> anything that is checked in to Arch.

I'd like to do this, but have been nervous to because of my uncertainity
about CVS's behavior.  If people think it's safe to use `-kb' globally
I'll do that (from from my reading of the docs a global `-ko' is
dangerous though, as it overrides a file-specific -kb setting, and so
could conceivably cause problems with binary files).

If I'm interpreting the docs correctly, BTW, switching to `-kb' will
leave expanded keywords in currently checked-out files unchanged (that
is, if CVS stores keywords unexpanded in the repository, adding `-kb'
_won't_ suddently cause keywords in checked out files to revert to their
unexpanded forms), which might be slightly confusing for anyone relying
on RCS keywords in bug reports.

> Alternatively, a feature to tell Arch to ignore certain kinds of
> differences could be implemented.

But I'm not going to do that.

Thanks,

-Miles
-- 
97% of everything is grunge