unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ken Manheimer <ken.manheimer@gmail.com>
Cc: 42218@debbugs.gnu.org
Subject: bug#42218: 28.0.50; Fix for missed item undecoration on allout-widgets-mode deactivation
Date: Mon, 20 Jul 2020 21:38:27 +0300	[thread overview]
Message-ID: <83k0yyghgc.fsf@gnu.org> (raw)
In-Reply-To: <CAAT_zTH-_5KtvSDDe3q5fZCFEo8gySyuRnbqw8YSmti_TACUqg@mail.gmail.com> (message from Ken Manheimer on Mon, 20 Jul 2020 13:56:27 -0400)

> From: Ken Manheimer <ken.manheimer@gmail.com>
> Date: Mon, 20 Jul 2020 13:56:27 -0400
> Cc: 42218@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.





  reply	other threads:[~2020-07-20 18:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-05 21:04 bug#42218: 28.0.50; Fix for missed item undecoration on allout-widgets-mode deactivation Ken Manheimer
2020-07-18  7:43 ` Eli Zaretskii
2020-07-20 17:56   ` Ken Manheimer
2020-07-20 18:38     ` Eli Zaretskii [this message]
2020-07-20 18:58       ` Ken Manheimer
2020-07-20 19:24         ` Eli Zaretskii
2020-07-20 19:28           ` Eli Zaretskii
2020-07-20 20:09             ` Ken Manheimer
2020-07-21  2:24               ` Eli Zaretskii
2020-07-21 15:17                 ` Ken Manheimer
2020-07-21 16:34                   ` Eli Zaretskii
     [not found] ` <handler.42218.B.159398312421153.ack@debbugs.gnu.org>
2020-07-20 19:15   ` bug#42218: Acknowledgement (28.0.50; Fix for missed item undecoration on allout-widgets-mode deactivation) Ken Manheimer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83k0yyghgc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=42218@debbugs.gnu.org \
    --cc=ken.manheimer@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).