GNU bug report logs - #42365
28.0.50; Eldoc misbehaves if eldoc-echo-area-use-multiline-p is not t

Previous Next

Full log

View this message in rfc822 format

From: João Távora <joaotavora <at> gmail.com>
To: Tassilo Horn <tsdh <at> gnu.org>
Cc: 42365-done <at> debbugs.gnu.org
Subject: bug#42365: 28.0.50; Eldoc misbehaves if eldoc-echo-area-use-multiline-p is not t
Date: Wed, 15 Jul 2020 20:37:31 +0100

Maybe that makes sense.  I don't care about ChangeLogs,
but I care a bit about the function listing (not terribly so,
but a bit, yes).

So maybe I would do:

; fix regression bug#xxxxx

* lisp/emacs-lisp/foo.lisp (bar): baz.

But if Eli doesn't complain, I'm not going to :-)

João

On Wed, Jul 15, 2020 at 8:34 PM Tassilo Horn <tsdh <at> gnu.org> wrote:
>
> João Távora <joaotavora <at> gmail.com> writes:
>
> > By the way, is it OK to put "; fix regression XXX" for a
> > commit message in these cases?  Just wondering.
>
> I don't know but until now, Eli has not complained. ;-)
>
> My stance is that your previous commit was the actual change whose
> message belongs into the ChangeLog.  My commit just fixed a minor aspect
> nobody except me had caught in the last five days, so probably no
> additional information worthy of a ChangeLog entry.
>
> Bye,
> Tassilo



-- 
João Távora

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.