From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: [PATCH] Implement Python backend for Flymake
Date: Fri, 13 Oct 2017 11:09:40 +0200 [thread overview]
Message-ID: <b449a8e7-d803-63f0-9b26-2a501d149a89@gmail.com> (raw)
In-Reply-To: <87y3of2zbj.fsf@metapensiero.it>
On 2017-10-13 11:04, Lele Gaifax wrote:
> Hi,
>
> here below you can find an implementation of a Python backend for the new
> Flymake facility.
Aren't patches supposed to go to bug-gnu-emacs?
Thanks :)
Clément.
next prev parent reply other threads:[~2017-10-13 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 9:04 [PATCH] Implement Python backend for Flymake Lele Gaifax
2017-10-13 9:09 ` Clément Pit-Claudel [this message]
2017-10-13 9:22 ` Lele Gaifax
2017-10-13 9:50 ` Eli Zaretskii
2017-10-13 9:52 ` Lele Gaifax
2017-10-18 18:06 ` Lele Gaifax
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=b449a8e7-d803-63f0-9b26-2a501d149a89@gmail.com \
--to=cpitclaudel@gmail.com \
--cc=emacs-devel@gnu.org \
/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).