From: Eli Zaretskii <eliz@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: sbaugh@janestreet.com, 64543@debbugs.gnu.org, sbaugh@catern.com
Subject: bug#64543: [PATCH] package-report-bug: don't fail on custom groups defined by eval
Date: Sat, 15 Jul 2023 08:49:21 +0300 [thread overview]
Message-ID: <83mszxenby.fsf@gnu.org> (raw)
In-Reply-To: <87fs5qp9bk.fsf@posteo.net> (message from Philip Kaludercic on Fri, 14 Jul 2023 19:44:15 +0000)
> From: Philip Kaludercic <philipk@posteo.net>
> Cc: sbaugh@catern.com, 64543@debbugs.gnu.org, "'Eli Zaretskii'" <eliz@gnu.org>
> Date: Fri, 14 Jul 2023 19:44:15 +0000
>
> Eli, would it be OK to push this to emacs-29, as this is a bug in the
> existing code? Most of the changes are indentation/whitespace changes
> anyway.
I don't understand the cases in which this bug happens, and so cannot
make the decision. The entire discussion of this bug never described
such a case, AFAICT. (Also, the commit log message could use some
loving care: what does it mean when it says "Previously"?)
next prev parent reply other threads:[~2023-07-15 5:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 17:08 bug#64543: [PATCH] package-report-bug: don't fail on custom groups defined by eval sbaugh
2023-07-10 14:13 ` Philip Kaludercic
2023-07-12 19:26 ` sbaugh
2023-07-12 19:48 ` Philip Kaludercic
2023-07-12 19:56 ` Spencer Baugh
2023-07-14 19:44 ` Philip Kaludercic
2023-07-15 5:49 ` Eli Zaretskii [this message]
2023-07-15 7:40 ` Philip Kaludercic
2023-07-15 8:57 ` Eli Zaretskii
2023-07-13 4:54 ` Eli Zaretskii
[not found] <c6bc281e-d6e5-4c5c-8315-157c6b089330@email.android.com>
2023-07-15 9:23 ` Eli Zaretskii
2023-07-15 10:05 ` Philip Kaludercic
2023-07-15 10:23 ` Eli Zaretskii
2023-07-15 23:33 ` Philip Kaludercic
2023-07-15 17:45 ` sbaugh
2023-07-16 12:33 ` Philip Kaludercic
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=83mszxenby.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64543@debbugs.gnu.org \
--cc=philipk@posteo.net \
--cc=sbaugh@catern.com \
--cc=sbaugh@janestreet.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).