From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: schwab@linux-m68k.org, 42790@debbugs.gnu.org, lin.sun@zoom.us
Subject: bug#42790: [PATH] 27.1; Add version info into file name "emacs.pdmp" to avoid mismatch pdmp file
Date: Sat, 27 Feb 2021 13:21:54 -0500 [thread overview]
Message-ID: <xba6rpe5h9.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83czwmotz6.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 27 Feb 2021 09:22:37 +0200")
Eli Zaretskii wrote:
> So delaying a release indefinitely due to such problems doesn't sound
> wise to me: we are already accused of having too long release cycles.
You control when a release is made. A flag in the bug database can't
prevent you from making a release. But if you don't have any mechanism
for communicating to people what you think the important issues are,
they are likely to get lost in the noise (certain individuals can report
a dozen trivial bugs a day). Personally I have no idea what issues
remain to be fixed before 27.2 can be released.
next prev parent reply other threads:[~2021-02-27 18:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 3:21 bug#42790: [PATH] 27.1; Add version info into file name "emacs.pdmp" to avoid mismatch pdmp file via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-08-10 8:27 ` Andreas Schwab
2020-08-10 9:24 ` via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-16 1:03 ` Glenn Morris
2020-11-20 15:07 ` Eli Zaretskii
2021-02-27 1:40 ` Glenn Morris
2021-02-27 7:22 ` Eli Zaretskii
2021-02-27 16:05 ` Daniel Colascione
2021-02-27 18:21 ` Glenn Morris [this message]
2021-02-27 18:49 ` Eli Zaretskii
2021-07-21 13:51 ` Lars Ingebrigtsen
2021-09-30 1:33 ` Glenn Morris
2021-09-30 6:47 ` Lars Ingebrigtsen
2021-10-11 12:04 ` Lars Ingebrigtsen
2020-08-14 14:53 ` Lars Ingebrigtsen
2020-08-15 4:52 ` via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-08-15 10:42 ` Lars Ingebrigtsen
2020-08-15 10:47 ` Lars Ingebrigtsen
2020-08-16 0:30 ` via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xba6rpe5h9.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=42790@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=lin.sun@zoom.us \
--cc=schwab@linux-m68k.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.