bug#33005: 27.0.50; Data loss with Gnus registry

[Eli Zaretskii]

> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: Eric Abrahamsen <eric@ericabrahamsen.net>,  33005@debbugs.gnu.org
> Date: Thu, 11 Oct 2018 22:08:08 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > I see you already did, and on the emacs-26 branch.  Please in the
> > future ask about commits to the release branch.
> 
> Some days ago I asked a question about the habits and expectations
> regarding bug fixes, in particular for bugs that were not introduced by
> the current release.  Nobody disagreed that committing to the release is
> just ok.  So it is not?

In general, it is.  But a bug fix should be safe enough to be eligible
for the release branch, and the "enough" part changes depending on the
state of the branch.  Currently, since Emacs 26.1 was already
released, only very safe fixes are eligible, and I'd like to be part
of the decision loop regarding the safety of each proposed fix.

> Why do you think people know what you expect?

Because I said it many times here.  The fact is, most people do ask.