From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: acm@muc.de, jayden@yugabyte.com, 36328@debbugs.gnu.org
Subject: bug#36328: 26.2; Args out of range on search-and-replace of *.cc file
Date: Fri, 05 Jul 2019 09:11:37 +0300 [thread overview]
Message-ID: <831rz5au3q.fsf@gnu.org> (raw)
In-Reply-To: <87ef35wlpg.fsf@mail.linkov.net> (message from Juri Linkov on Fri, 05 Jul 2019 00:09:47 +0300)
> From: Juri Linkov <juri@linkov.net>
> Cc: Alan Mackenzie <acm@muc.de>, Jayden Navarro <jayden@yugabyte.com>, 36328@debbugs.gnu.org
> Date: Fri, 05 Jul 2019 00:09:47 +0300
>
> Eli, do you think this fix should be pushed to emacs-26?
I'd like to avoid any code changes on the branch that aren't 110%
necessary. We should release 26.3 ASAP, otherwise Emacs 27 will wait
for too long.
Sorry.
next prev parent reply other threads:[~2019-07-05 6:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 23:03 bug#36328: 26.2; Args out of range on search-and-replace of *.cc file Jayden Navarro
[not found] ` <mailman.612.1561158667.10840.bug-gnu-emacs@gnu.org>
2019-06-22 13:25 ` Alan Mackenzie
2019-06-22 14:25 ` Jayden Navarro
2019-06-22 14:51 ` Juanma Barranquero
2019-06-22 16:09 ` Jayden Navarro
2019-06-22 20:50 ` Alan Mackenzie
2019-06-22 21:27 ` Jayden Navarro
2019-06-22 22:38 ` Jayden Navarro
2019-06-22 23:02 ` Jayden Navarro
2019-06-23 12:22 ` Alan Mackenzie
2019-06-23 16:14 ` Jayden Navarro
2019-06-23 19:32 ` Alan Mackenzie
2019-06-23 21:19 ` Juri Linkov
2019-06-23 21:42 ` Jayden Navarro
2019-06-24 19:05 ` Juri Linkov
2019-06-24 20:03 ` Jayden Navarro
2019-06-24 7:52 ` Alan Mackenzie
2019-06-24 19:18 ` Juri Linkov
2019-06-25 9:47 ` Alan Mackenzie
2019-06-25 19:58 ` Juri Linkov
2019-07-04 21:09 ` Juri Linkov
2019-07-05 6:11 ` Eli Zaretskii [this message]
2019-07-05 19:12 ` Juri Linkov
2019-10-02 23:53 ` Stefan Kangas
2019-06-23 20:10 ` bug#36328: [jayden@yugabyte.com: Re: bug#36328: 26.2; Args out of range on search-and-replace of *.cc file] Alan Mackenzie
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=831rz5au3q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36328@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=jayden@yugabyte.com \
--cc=juri@linkov.net \
/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.