From: Lele Gaifax <lele@metapensiero.it>
To: emacs-devel@gnu.org
Subject: Re: [PATCH] Implement Python backend for Flymake
Date: Wed, 18 Oct 2017 20:06:09 +0200 [thread overview]
Message-ID: <87y3o8covi.fsf@metapensiero.it> (raw)
In-Reply-To: 87po9r2x4o.fsf@metapensiero.it
Lele Gaifax <lele@metapensiero.it> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> It's preferred to send to bug-gnu-emacs, yes. The reason is that
>> doing so provides a reference that's easy to cite in a log message.
>> It also allows to produce various reports using the debbugs features.
>
> Ok, doing that immediately.
I went ahead on this, my latest version is here:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=28808#23
Please let me know if there's anything else I could/should do.
Thanks&bye, lele.
--
nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri
real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia.
lele@metapensiero.it | -- Fortunato Depero, 1929.
next prev parent reply other threads:[~2017-10-18 18:06 UTC|newest]
Thread overview: 17+ 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
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 [this message]
2017-10-13 20:56 ` bug#28821: " João Távora
[not found] ` <handler.28821.B.150792820417597.ack@debbugs.gnu.org>
2017-10-13 21:00 ` bug#28821: Acknowledgement ([PATCH] Implement Python backend for Flymake) João Távora
2017-10-13 21:03 ` bug#28808: [PATCH] Implement Python backend for Flymake João Távora
2017-10-14 8:15 ` Lele Gaifax
2017-10-14 9:14 ` João Távora
2017-10-17 21:58 ` Lele Gaifax
2017-10-21 7:15 ` bug#28808: Consider the right python--flymake-proc Lele Gaifax
2017-10-21 13:05 ` João Távora
2017-11-03 12:24 ` João Távora
2017-11-03 19:16 ` Lele Gaifax
2017-10-13 21:13 ` bug#28821: Closing this bug created in error João Távora
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=87y3o8covi.fsf@metapensiero.it \
--to=lele@metapensiero.it \
--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 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.