all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael_heerdegen@web.de,  emacs-devel@gnu.org
Subject: Re: bug#60893: 30.0.50; ad-deactive has broken interactive TAB completion
Date: Fri, 20 Jan 2023 16:50:13 +0100	[thread overview]
Message-ID: <87sfg5yzm2.fsf@gmail.com> (raw)
In-Reply-To: <83pmb9mdy3.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 20 Jan 2023 17:19:00 +0200")

>>>>> On Fri, 20 Jan 2023 17:19:00 +0200, Eli Zaretskii <eliz@gnu.org> said:

    >> From: Robert Pluim <rpluim@gmail.com>
    >> Cc: Michael Heerdegen <michael_heerdegen@web.de>,
    >> "emacs-devel" <emacs-devel@gnu.org>
    >> Date: Fri, 20 Jan 2023 16:11:25 +0100
    >> 
    >> 
    >> >>>>> On Fri, 20 Jan 2023 15:48:53 +0200, Eli Zaretskii <eliz@gnu.org> said:
    >> 
    >> >> From: Michael Heerdegen <michael_heerdegen@web.de>
    >> >> Cc: hmelman@gmail.com,  60893@debbugs.gnu.org
    >> >> Date: Fri, 20 Jan 2023 14:27:44 +0100
    >> >> 
    >> >> Eli Zaretskii <eliz@gnu.org> writes:
    >> >> 
    >> >> > I already cherry-picked that commit to the emacs-29 branch yesterday.
    >> >> 
    >> >> Thanks 🙏.
    >> >> 
    >> >> I see you edited the commit message and removed an empty line.  We
    >> >> prefer to not have an empty line between the second paragraph with
    >> >> explanations and the individual files section, is this correct?
    >> 
    Eli> Yes.
    >> 
    >> We do? Thatʼs not at all obvious from eg CONTRIBUTE
    >> 
    >> (I happen to disagree, but I donʼt make the rules)

    Eli> It's not a strong preference, so don't expect me to mount the
    Eli> barricades over this.

Mine is not that strong either, so we can just leave things as-is.

Robert
-- 



      reply	other threads:[~2023-01-20 15:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 20:21 bug#60893: 30.0.50; ad-deactive has broken interactive TAB completion Dima Kogan
2023-01-18  5:03 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-18  5:12   ` Dima Kogan
2023-01-18  6:22     ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-18 11:34 ` Michael Heerdegen
2023-01-19  5:35   ` Dima Kogan
2023-01-19 18:57     ` Michael Heerdegen
2023-01-19 21:21       ` Howard Melman
2023-01-19 23:37         ` Michael Heerdegen
2023-01-20  6:50           ` Eli Zaretskii
2023-01-20 13:27             ` Michael Heerdegen
2023-01-20 13:48               ` Eli Zaretskii
2023-01-20 15:11                 ` Robert Pluim
2023-01-20 15:19                   ` Eli Zaretskii
2023-01-20 15:50                     ` Robert Pluim [this message]

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

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

  git send-email \
    --in-reply-to=87sfg5yzm2.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.