>>>> "nix" == nix
nix> [moved to xemacs-beta; this is not a patch anymore]]
nix> On 27 Dec 2001, Adrian Aichner moaned:
> this veto is only against the ChangeLog entry.
boggle not for I am no bugbear!
> Please reformat it to become compliant with
> (xemacs)Change Log
nix> A point of policy: many other projects accept multiline changelog
nix> headers to indicate multiperson authorship. For instance (from GCC):
nix> 2001-08-13 Roman Zippel <zippel(a)linux-m68k.org>
nix> Richard Henderson <rth(a)redhat.com>
nix> * regmove.c (regmove_optimize): Avoid setting a register twice in
nix> a parallel set.
nix> So this is a divergence from GNU ;)
XEmacs is a divergence from GNU,
and a pretty good one too :-)
nix> IMHO, this is the only fair way to indicate true multiperson
nix> authorship of a patch. In this case, I could probably
nix> rephrase it as
I did not miss your point.
nix> 2001-12-26 Nix <nix(a)esperi.demon.co.uk>
nix> * uniquify.el (uniquify-ignore-buffers-query-functions): New hook,
nix> called to determine buffers not to uniquify. (Thanks to Volker
nix> Franz <volker.franz(a)tuebingen.mpg.de>
nix> (uniquify-rationalize-file-buffer-names): Use it...
nix> (uniquify-ignore-buffers-re): ... reimplement in terms of it.
nix> New function.
nix> (uniquify-ignore-buffers-mode-re): New variable and function.
nix> but if Volker had changed most of the patch, this could get extremely
> The header should be a single line:
>> A change log entry starts with a header line that contains your name
>> and the current date. Except for these header lines, every line in the
>> change log starts with a tab. One entry can describe several changes;
>> each change starts with a line starting with a tab and a star. `M-x
nix> What is the rationale for this? The GNU coding standards
Stephen already gave a good explanation.
Until we get a proposal for extending the XEmacs changlog format
approved, programs and documentation changed, we will have to veto
violations of the current standard.
nix> carefully avoid describing the precise format of a changelog
nix> entry (and, in fact, even this ext doesn't describe things
nix> like the format of date to be used, and several different
nix> formats are in use.)
Yes, and all this sucks :-)
Nix, if you feel strongly enough about this, why don't you write up a
proposal for combining best practices in changelog land and get it
approved by xemacs-review? You don't need to implement the solution,
but a good proposal would be a good starting point for the
Thanks for stirring this up!
nix> `Mmm... Maybe I just like strong women that can hurt me?'
nix> --- Vadik, on female throat-cutting doctors