unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: enometh@meer.net, 31695@debbugs.gnu.org
Subject: bug#31695: bug-gnu-emacs@gnu.org
Date: Fri, 08 Jun 2018 11:18:14 +0300	[thread overview]
Message-ID: <83po11vghl.fsf@gnu.org> (raw)
In-Reply-To: <5B1A37AA.6060801@gmx.at> (message from martin rudalics on Fri, 08 Jun 2018 10:00:42 +0200)

> Date: Fri, 08 Jun 2018 10:00:42 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: enometh@meer.net, 31695@debbugs.gnu.org
> 
>  > So unless you are really, REALLY sure this should go to emacs-26, I'd
>  > prefer to have it on master, and let the dust settle on it before we
>  > decide it's TRT.
> 
> The only justifiable alternative I see is to revert the fix for
> Bug#12208 on Emacs 26 since that bug is even more obscure than the
> present one.

I see no reason to revert the fix for 12208, so emacs-26 it is.
Thanks.

> But whatever you decide the responsibility will be all mine.

That's not what I was worried about ;-)





  reply	other threads:[~2018-06-08  8:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-03  4:47 bug#31695: bug-gnu-emacs@gnu.org Madhu
2018-06-03 12:21 ` martin rudalics
2018-06-03 16:38   ` Eli Zaretskii
2018-06-04 16:29     ` Eli Zaretskii
2018-06-05 13:36       ` martin rudalics
2018-06-04 20:40   ` Gemini Lasswell
2018-06-05 13:37     ` martin rudalics
2018-06-07  8:39 ` martin rudalics
2018-06-07 15:30   ` Eli Zaretskii
2018-06-08  8:00     ` martin rudalics
2018-06-08  8:18       ` Eli Zaretskii [this message]
     [not found]       ` <<83po11vghl.fsf@gnu.org>
2018-06-08 13:58         ` Drew Adams
2018-06-08 14:36           ` Eli Zaretskii
2018-06-08 14:38           ` Robert Pluim
     [not found]       ` <<<83po11vghl.fsf@gnu.org>
     [not found]         ` <<0b7a8176-03d2-4efd-bf60-e193e8433f85@default>
     [not found]           ` <<83a7s5uyzi.fsf@gnu.org>
2018-06-08 14:47             ` Drew Adams
2018-06-14  3:32   ` bug#31695: minibuffer command takes window-point from another frame displaying the same buffer Noam Postavsky

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83po11vghl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=31695@debbugs.gnu.org \
    --cc=enometh@meer.net \
    --cc=rudalics@gmx.at \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).