GNU bug report logs - #42218
28.0.50; Fix for missed item undecoration on allout-widgets-mode deactivation

Previous Next

Full log

Message #14 received at 42218 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ken Manheimer <ken.manheimer <at> gmail.com>
Cc: 42218 <at> debbugs.gnu.org
Subject: Re: bug#42218: 28.0.50; Fix for missed item undecoration on
 allout-widgets-mode deactivation
Date: Mon, 20 Jul 2020 21:38:27 +0300

> From: Ken Manheimer <ken.manheimer <at> gmail.com>
> Date: Mon, 20 Jul 2020 13:56:27 -0400
> Cc: 42218 <at> debbugs.gnu.org
> 
> To make sure I'm doing the right thing, I plan to merge the local branches where I have my various fixes
> (after rebasing them on current master) to my local clone of master, and then push it all back to Savannah. I
> will also merge to the emacs-27 branch and push that, and close the related bug reports. Is this correct?

The emacs-27 branch should only get documentation fixes and very safe
bugfixes for serious bugs.  Other than that, please don't push
anything there; when in doubt, please ask.

> One other question. I have a few more allout-widgets.el patches that are development-related, and as such
> don't solve any bugs. I would like to push them out, as well. Is it preferred that I associate them with a bug
> report, or is it sufficient for me to just be clear in the commit messages, without any bug report?

A bug report is always preferable (and then please mention its number
in the commit log), as it leaves an easily identifiable trace.

Thanks.

Previous Next

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