GNU bug report logs - #42790
[PATH] 27.1; Add version info into file name "emacs.pdmp" to avoid mismatch pdmp file

Previous Next

Full log

Message #52 received at 42790 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Glenn Morris <rgm <at> gnu.org>
Cc: dancol <at> dancol.org, schwab <at> linux-m68k.org, 42790 <at> debbugs.gnu.org,
 lin.sun <at> zoom.us
Subject: Re: bug#42790: [PATH] 27.1;
 Add version info into file name "emacs.pdmp" to avoid mismatch pdmp
 file
Date: Sat, 27 Feb 2021 09:22:37 +0200

> From: Glenn Morris <rgm <at> gnu.org>
> Cc: Daniel Colascione <dancol <at> dancol.org>,  42790 <at> debbugs.gnu.org,  schwab <at> linux-m68k.org,  lin.sun <at> zoom.us
> Date: Fri, 26 Feb 2021 20:40:22 -0500
> 
> Eli Zaretskii wrote:
> 
> > I hope this gets cleaned up, because I think it would be good to have
> > this fixed for Emacs 27.2.
> 
> No response; presumably it's now too late.

Yes, pretty much.

> (FWIW I think it would be straightforward for someone whose C isn't
> execrable like mine.)
> 
> I really think having some central list of "issues that should be fixed
> before the next release" would help with this kind of thing.
> 
> The debbugs blocking mechanism has been used for this previously.
> If you don't like it that's fine, please use whatever you prefer.
> Eg monthly summary postings to emacs-devel, anything.

It's okay to use debbugs blocking, but the problem is, we have no real
mechanism to make sure the blocking problems will be worked on, and
the fact that some aren't is an indirect evidence that those problems
aren't acute.  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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.