From: Matthias Meulien <orontee@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: arstoffel@gmail.com, 64406@debbugs.gnu.org
Subject: bug#64406: [PATCH] Improve commands to manage Python imports
Date: Sun, 09 Jul 2023 09:54:12 +0200 [thread overview]
Message-ID: <877cr934gr.fsf@gmail.com> (raw)
In-Reply-To: <838rbpbl2h.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 09 Jul 2023 10:28:22 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> (...) 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.
Ok, I understand.
> 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.
No, I hadn't read that file. Thanks for the reference.
--
Matthias
next prev parent reply other threads:[~2023-07-09 7:54 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
2023-07-09 7:54 ` Matthias Meulien [this message]
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=877cr934gr.fsf@gmail.com \
--to=orontee@gmail.com \
--cc=64406@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
--cc=eliz@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).