From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
"emacs-devel" <emacs-devel@gnu.org>
Subject: Re: bug#60893: 30.0.50; ad-deactive has broken interactive TAB completion
Date: Fri, 20 Jan 2023 16:11:25 +0100 [thread overview]
Message-ID: <871qnp1bs2.fsf@gmail.com> (raw)
In-Reply-To: <83wn5hmi4a.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 20 Jan 2023 15:48:53 +0200")
redirecting to emacs-devel
>>>>> 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)
Robert
--
next parent reply other threads:[~2023-01-20 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87lem09ajl.fsf@secretsauce.net>
[not found] ` <87zgaghy90.fsf@web.de>
[not found] ` <87r0vr6q63.fsf@secretsauce.net>
[not found] ` <87y1py73nu.fsf@web.de>
[not found] ` <lysfg6b4qj.fsf@new-host-2.home>
[not found] ` <87pmba6qq3.fsf@web.de>
[not found] ` <83k01hog1x.fsf@gnu.org>
[not found] ` <87k01h72un.fsf@web.de>
[not found] ` <83wn5hmi4a.fsf@gnu.org>
2023-01-20 15:11 ` Robert Pluim [this message]
2023-01-20 15:19 ` bug#60893: 30.0.50; ad-deactive has broken interactive TAB completion Eli Zaretskii
2023-01-20 15:50 ` Robert Pluim
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=871qnp1bs2.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 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).