From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>, Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Patches for Emacs 25.2
Date: Tue, 18 Oct 2016 10:24:38 +0300 [thread overview]
Message-ID: <837f96xgp5.fsf@gnu.org> (raw)
In-Reply-To: <877f96t9oc.fsf@gmx.de> (message from Michael Albinus on Tue, 18 Oct 2016 09:09:55 +0200)
> From: Michael Albinus <michael.albinus@gmx.de>
> Date: Tue, 18 Oct 2016 09:09:55 +0200
>
> yesterday, I've shown two candidate patches for Tramp (bug#24698,
> bug#24478). Given, that there will be an Emacs 25.2 soon, I'm undecided
> whether they shall go into the emacs-25 branch, once confirmed by the
> bug reporters. Any policy for that?
I described what I thought should be the policy here:
http://lists.gnu.org/archive/html/emacs-devel/2016-10/msg00007.html
to which no one objected.
Bug#24478 is listed as blocking 25.2 release, so its fix should
definitely go to the emacs-25 branch. But I understand you are still
waiting for Glenn to tell whether the solution is correct?
Not sure about bug#24698. Does it fit the criteria described in the
above message?
> Will there be a test period for Emacs 25.2?
Yes, but I'd like it to be very short. If possible, I'd like to start
the 25.2 pretest in a couple of weeks.
> One policy could be, that only fixes shall be pushed to the emacs-25
> branch for bugs which have been marked as blocking bug#21966. In this
> case, what would be the policy to add a bug there? bug#24478 belongs to
> that list already, bug#24698 doesn't.
See above. Not every bug that fits the criteria is listed as
blocking, primarily because we simply failed to mark them as blocking.
Thanks.
next prev parent reply other threads:[~2016-10-18 7:24 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 7:09 Patches for Emacs 25.2 Michael Albinus
2016-10-18 7:24 ` Eli Zaretskii [this message]
2016-10-18 7:47 ` Michael Albinus
2016-10-18 8:09 ` Nikolay Kudryavtsev
2016-10-18 8:25 ` Michael Albinus
2016-10-18 9:24 ` Eli Zaretskii
2016-10-18 11:05 ` Nikolay Kudryavtsev
2016-10-18 11:29 ` Eli Zaretskii
2016-10-18 11:59 ` Nikolay Kudryavtsev
2016-10-18 12:32 ` Michael Albinus
2016-10-18 14:38 ` Eli Zaretskii
2016-11-07 0:08 ` Dmitry Gutov
2016-11-07 9:01 ` Michael Albinus
2016-11-07 9:36 ` Dmitry Gutov
2016-11-07 10:31 ` Michael Albinus
2016-11-07 10:39 ` Dmitry Gutov
2016-11-07 10:58 ` Michael Albinus
2016-11-19 23:03 ` Dmitry Gutov
2016-11-20 15:34 ` file-local-name (was: Patches for Emacs 25.2) Michael Albinus
2016-11-19 23:04 ` Patches for Emacs 25.2 Dmitry Gutov
2016-11-20 8:49 ` Michael Albinus
2016-12-31 4:20 ` Nikolay Kudryavtsev
2016-12-31 11:32 ` Dmitry Gutov
2016-12-31 11:40 ` Eli Zaretskii
2016-12-31 11:44 ` Dmitry Gutov
2017-01-02 10:21 ` Nikolay Kudryavtsev
2017-01-02 10:32 ` Dmitry Gutov
2017-01-02 12:22 ` Michael Albinus
2017-01-02 18:43 ` Nikolay Kudryavtsev
2017-01-02 18:54 ` Michael Albinus
2017-01-02 19:08 ` Dmitry Gutov
2017-01-02 19:56 ` Michael Albinus
2017-01-02 20:08 ` Dmitry Gutov
2017-01-02 19:54 ` Michael Albinus
2017-01-02 20:52 ` Nikolay Kudryavtsev
2017-01-02 19:13 ` Dmitry Gutov
2016-10-18 9:13 ` Eli Zaretskii
2016-10-18 9:55 ` Michael Albinus
2016-10-18 10:05 ` Eli Zaretskii
2016-10-18 11:24 ` Michael Albinus
2016-10-18 11:30 ` Eli Zaretskii
2016-12-16 0:05 ` Dmitry Gutov
2016-12-16 8:10 ` Eli Zaretskii
2016-12-16 18:33 ` Dmitry Gutov
2016-12-16 21:11 ` Eli Zaretskii
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=837f96xgp5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=rgm@gnu.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.