From: Lars Ingebrigtsen <larsi@gnus.org>
To: Martin Puttke <martinstefanputtke@posteo.de>
Cc: 46817@debbugs.gnu.org
Subject: bug#46817: update python grammar
Date: Wed, 03 Mar 2021 15:52:18 +0100 [thread overview]
Message-ID: <874khsxpb1.fsf@gnus.org> (raw)
In-Reply-To: <874kht4edo.fsf@posteo.de> (Martin Puttke's message of "Tue, 02 Mar 2021 19:08:51 +0100")
Martin Puttke <martinstefanputtke@posteo.de> writes:
> thank you for your offer to do the FSF paperwork. But at the moment I
> have no plans to submit another patch to emacs. It may come, but I
> prefer to do it when needed.
Sure; that's fine.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-03-03 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 18:04 bug#46817: update python grammar Martin Puttke
2021-02-28 14:22 ` Lars Ingebrigtsen
2021-03-02 18:08 ` Martin Puttke
2021-03-03 14:52 ` Lars Ingebrigtsen [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
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=874khsxpb1.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=46817@debbugs.gnu.org \
--cc=martinstefanputtke@posteo.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).