Re: Gnus overrides.texi and WEBHACKDEVEL

[Eli Zaretskii]

> From: Ted Zlatanov <address@hidden>
> Date: Sat, 05 Feb 2011 08:21:18 -0600
> Cc: address@hidden
> 
> Now, overrides.texi is for Gnus manuals overrides: settings we may want
> to propagate to all our manuals.  So I think it makes sense to have it,
> just not the way I did it with shell redirection.  I renamed it to
> gnus-overrides.texi and it can be used for things we want to use in all
> the Gnus manuals in the future.  I hope that's OK with everyone; if not
> it's easy enough to pull that include out.

I don't necessarily see a problem, but I don't understand why you need
a .texi file for these overrides.  At least the "@set FOO" part of
those overrides can be easily handled by add -DFOO switch to
MAKEINFO_OPTS.

More generally, what is a user supposed to do if she does want to put
something on gnus-overrides.texi?  That's a versioned file, so "bzr
status" will show it as modified, and there's still a danger of having
it committed inadvertently.  How is this better than just modifying
gnu.texi or any other file directly?