From: Eli Zaretskii <eliz@gnu.org>
To: Matthias Meulien <orontee@gmail.com>
Cc: arstoffel@gmail.com, 64406@debbugs.gnu.org
Subject: bug#64406: [PATCH] Improve commands to manage Python imports
Date: Sun, 09 Jul 2023 10:28:22 +0300 [thread overview]
Message-ID: <838rbpbl2h.fsf@gnu.org> (raw)
In-Reply-To: <CAFEQCfBHfL680oYFgN7jSRdkT-hCDGjtJMYhCxyO5SJ1W5iq4A@mail.gmail.com> (message from Matthias Meulien on Sun, 9 Jul 2023 08:32:09 +0200)
> From: Matthias Meulien <orontee@gmail.com>
> Date: Sun, 9 Jul 2023 08:32:09 +0200
> Cc: 64406@debbugs.gnu.org, Augusto Stoffel <arstoffel@gmail.com>
>
> Sorry Eli for asking such trivial question but I didn't manage to find hints on the web: Now that this bug
> is tagged as done, should I create a new bug for last two patches or is it possible to reopen?
No need to submit a new bug, if the discussion is still about the same
issue. Reopening is appropriate if the original bug is deemed not
fixed; otherwise, just keep CC'ing the bug number, even so it is
closed.
IOW, "closed" doesn't mean the discussion cannot go on, and also
doesn't mean we cannot augment the solution by additional fixes for
whatever leftovers we find.
Did you read admin/notes/bugtracker? It might have cleared up some of
this. It also explains how to reopen a bug if you need that.
next prev parent reply other threads:[~2023-07-09 7:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 20:16 bug#64406: [PATCH] Improve commands to manage Python imports Matthias Meulien
2023-07-06 7:28 ` Eli Zaretskii
2023-07-07 17:02 ` Augusto Stoffel
2023-07-07 17:46 ` Matthias Meulien
2023-07-09 6:09 ` Matthias Meulien
2023-07-09 6:32 ` Matthias Meulien
2023-07-09 7:28 ` Eli Zaretskii [this message]
2023-07-09 7:54 ` Matthias Meulien
2023-07-13 6:07 ` Eli Zaretskii
2023-07-13 21:07 ` Matthias Meulien
2023-07-15 8:25 ` Eli Zaretskii
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=838rbpbl2h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64406@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
--cc=orontee@gmail.com \
/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).