From: Tanguy Le Carrour <tanguy@bioneland.org>
To: 42395@debbugs.gnu.org
Subject: [bug#42395] Acknowledgement ([PATCH 1/2] gnu: Add python-mypy-extensions.)
Date: Fri, 17 Jul 2020 10:39:40 +0200 [thread overview]
Message-ID: <20200717083940.jatlycln4aii7ijt@rafflesia> (raw)
In-Reply-To: <handler.42395.B.159491010827194.ack@debbugs.gnu.org>
Hi Guix!
I've just found out that there's already a bug report with a patch series
for `python-mypy`: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=35193.
But it's more than a year old now, and has never been closed.
So I guess you can close this bug (#42395) and I'll start again where
Jesse left off. This means I have to enable and fix mypy's tests… which will
end up in adding some more new packages.
I'll (properly) open a new bug report when the patch set is ready.
Sorry (again) for the noise!
--
Tanguy
next prev parent reply other threads:[~2020-07-17 8:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 14:34 [bug#42395] [PATCH 1/2] gnu: Add python-mypy-extensions Tanguy Le Carrour
2020-07-16 14:34 ` [bug#42396] [PATCH 2/2] gnu: Add python-mypy Tanguy Le Carrour
[not found] ` <handler.42396.B.159491011027203.ack@debbugs.gnu.org>
2020-07-16 14:43 ` [bug#42396] Acknowledgement ([PATCH 2/2] gnu: Add python-mypy.) Tanguy Le Carrour
2020-07-22 12:02 ` bug#42396: [PATCH 2/2] gnu: Add python-mypy Tanguy Le Carrour
2020-07-16 14:40 ` [bug#42395] [PATCH v2 1/2] gnu: Add python-mypy-extensions Tanguy Le Carrour
2020-07-16 14:40 ` [bug#42395] [PATCH v2 2/2] gnu: Add python-mypy Tanguy Le Carrour
[not found] ` <handler.42395.B.159491010827194.ack@debbugs.gnu.org>
2020-07-17 8:39 ` Tanguy Le Carrour [this message]
2020-07-21 21:24 ` bug#42395: Acknowledgement ([PATCH 1/2] gnu: Add python-mypy-extensions.) Marius Bakke
2020-07-22 5:44 ` [bug#42395] " Tanguy Le Carrour
2020-07-25 15:43 ` Marius Bakke
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200717083940.jatlycln4aii7ijt@rafflesia \
--to=tanguy@bioneland.org \
--cc=42395@debbugs.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/guix.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).