From: Sean Whitton <spwhitton@spwhitton.name>
To: Xiyue Deng <manphiz@gmail.com>
Cc: debian-python@lists.debian.org, notmuch@notmuchmail.org,
mailscripts@packages.debian.org,
Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Subject: Re: Anyone interested in python-pgpy?
Date: Sun, 08 Dec 2024 13:08:15 +0800 [thread overview]
Message-ID: <87wmgakbi8.fsf@melete.silentflame.com> (raw)
In-Reply-To: <87ed2irigl.fsf@debian-hx90.lan> (Xiyue Deng's message of "Sat, 07 Dec 2024 18:56:10 -0800")
[-- Attachment #1.1: Type: text/plain, Size: 652 bytes --]
Hello,
On Sat 07 Dec 2024 at 06:56pm -08, Xiyue Deng wrote:
> I was thinking about keeping the bug open and downgrade to important so
> that we keep tracking it. But as I have forwarded it upstream we can
> monitor the upstream bug directly.
I think that downgrading it like that would make sense were you the
maintainer. But given that we're doing an NMU to deal with RC bugs,
just closing is a simpler documentation of your intent. The maintainer
might reopen it and downgrade its importance later.
Great work figuring out and then documenting these fixes.
mailscripts' dependency on python3-pgpy lives on!
--
Sean Whitton
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 869 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2024-12-08 5:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 2:56 Anyone interested in python-pgpy? Sean Whitton
2024-12-02 21:28 ` Xiyue Deng
2024-12-03 2:34 ` Sean Whitton
2024-12-03 18:22 ` Xiyue Deng
2024-12-04 9:18 ` Xiyue Deng
2024-12-05 2:35 ` Sean Whitton
2024-12-05 4:03 ` Xiyue Deng
2024-12-06 2:50 ` Sean Whitton
2024-12-06 20:40 ` Xiyue Deng
2024-12-07 8:59 ` Sean Whitton
2024-12-07 10:27 ` Xiyue Deng
2024-12-08 1:34 ` Sean Whitton
2024-12-08 2:56 ` Xiyue Deng
2024-12-08 5:08 ` Sean Whitton [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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wmgakbi8.fsf@melete.silentflame.com \
--to=spwhitton@spwhitton.name \
--cc=debian-python@lists.debian.org \
--cc=dkg@fifthhorseman.net \
--cc=mailscripts@packages.debian.org \
--cc=manphiz@gmail.com \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).