From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: eric@ericabrahamsen.net, 33005@debbugs.gnu.org
Subject: bug#33005: 27.0.50; Data loss with Gnus registry
Date: Fri, 12 Oct 2018 07:24:51 +0300 [thread overview]
Message-ID: <83va67x04s.fsf@gnu.org> (raw)
In-Reply-To: <8736tcz1p3.fsf@web.de> (message from Michael Heerdegen on Thu, 11 Oct 2018 22:08:08 +0200)
> 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.
next prev parent reply other threads:[~2018-10-12 4:24 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 13:24 bug#33005: 27.0.50; Data loss with Gnus registry Michael Heerdegen
2018-10-10 14:56 ` Eric Abrahamsen
2018-10-10 15:17 ` Michael Heerdegen
2018-10-10 16:08 ` Eric Abrahamsen
2018-10-10 20:23 ` Michael Heerdegen
2018-10-10 21:24 ` Michael Heerdegen
2018-10-10 23:05 ` Eric Abrahamsen
2018-10-11 12:44 ` Michael Heerdegen
2018-10-11 13:10 ` Michael Heerdegen
2018-10-11 18:12 ` Eric Abrahamsen
2018-10-11 20:28 ` Michael Heerdegen
2018-10-11 22:09 ` Eric Abrahamsen
2018-10-11 22:20 ` Michael Heerdegen
2018-10-11 22:26 ` Eric Abrahamsen
2018-10-12 14:22 ` Michael Heerdegen
2018-10-12 16:57 ` Eric Abrahamsen
2018-10-11 18:53 ` Eli Zaretskii
2018-10-11 18:57 ` Eric Abrahamsen
2018-10-11 20:08 ` Michael Heerdegen
2018-10-12 4:24 ` Eli Zaretskii [this message]
2018-10-12 11:04 ` Michael Heerdegen
2018-10-12 12:51 ` Eli Zaretskii
2018-10-12 14:46 ` Michael Heerdegen
2018-10-12 16:58 ` Eric Abrahamsen
2019-09-24 1:35 ` Michael Heerdegen
2019-09-24 3:34 ` Eric Abrahamsen
2019-10-01 23:37 ` Eric Abrahamsen
2019-10-14 9:53 ` Michael Heerdegen
2019-10-14 17:51 ` Eric Abrahamsen
2019-10-15 14:28 ` Michael Heerdegen
2019-10-15 20:11 ` Eric Abrahamsen
2019-10-16 9:03 ` Michael Heerdegen
2019-10-16 15:46 ` Eric Abrahamsen
2019-10-17 8:21 ` Michael Heerdegen
2019-10-17 15:53 ` Eric Abrahamsen
2019-10-18 9:18 ` Michael Heerdegen
2019-10-18 14:44 ` Michael Heerdegen
2019-10-19 2:05 ` Phil Sainty
2019-10-19 14:31 ` Michael Heerdegen
2019-10-19 22:12 ` Phil Sainty
2019-10-26 8:02 ` Michael Heerdegen
2019-10-26 15:35 ` Eric Abrahamsen
2019-11-18 9:17 ` Phil Sainty
2019-10-18 14:46 ` Michael Heerdegen
2019-10-18 19:07 ` Eric Abrahamsen
2019-10-18 19:09 ` Eric Abrahamsen
2019-10-18 19:23 ` Michael Heerdegen
2019-10-18 19:24 ` Eric Abrahamsen
2019-10-19 14:25 ` Michael Heerdegen
2019-10-19 18:06 ` Eric Abrahamsen
2019-10-18 19:06 ` Eric Abrahamsen
2019-10-16 9:30 ` Michael Heerdegen
2019-10-16 15:49 ` Eric Abrahamsen
2019-10-17 8:32 ` Michael Heerdegen
2019-10-17 10:23 ` Michael Heerdegen
2019-10-17 15:54 ` Eric Abrahamsen
2019-10-18 3:08 ` Richard Stallman
2019-10-18 9:50 ` Michael Heerdegen
2019-11-26 0:17 ` Michael Heerdegen
2019-11-26 0:51 ` Eric Abrahamsen
2019-11-26 16:32 ` Michael Heerdegen
2019-11-26 18:45 ` Eric Abrahamsen
2019-11-26 20:08 ` Michael Heerdegen
2019-11-26 20:41 ` Eric Abrahamsen
2019-11-26 20:45 ` Michael Heerdegen
2019-11-26 20:48 ` Eric Abrahamsen
2019-11-26 20:54 ` Michael Heerdegen
2019-11-28 8:43 ` Eric Abrahamsen
2019-11-28 16:25 ` Michael Heerdegen
2019-11-28 23:55 ` Eric Abrahamsen
2019-11-29 12:36 ` Michael Heerdegen
2019-12-03 9:19 ` Eric Abrahamsen
2019-12-04 16:10 ` Michael Heerdegen
2019-12-04 17:26 ` Eric Abrahamsen
2019-12-04 20:41 ` Michael Heerdegen
2019-12-04 20:53 ` Eric Abrahamsen
2019-12-04 21:02 ` Michael Heerdegen
2019-12-04 21:16 ` Eric Abrahamsen
2019-12-04 21:51 ` Michael Heerdegen
2019-12-05 0:51 ` Eric Abrahamsen
2019-12-08 15:48 ` Michael Heerdegen
2019-12-08 20:52 ` Eric Abrahamsen
2019-12-09 19:38 ` Michael Heerdegen
2019-12-09 22:29 ` Eric Abrahamsen
2019-12-09 23:07 ` Michael Heerdegen
2019-12-10 0:24 ` Eric Abrahamsen
2019-12-10 2:30 ` Michael Heerdegen
2019-12-10 23:31 ` Eric Abrahamsen
2019-12-15 17:07 ` Michael Heerdegen
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=83va67x04s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33005@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=michael_heerdegen@web.de \
/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.