unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: Brian Leung <leungbk@posteo.net>,
	Lars Ingebrigtsen <larsi@gnus.org>,
	53853@debbugs.gnu.org
Subject: bug#53853: [PATCH] Don't use string-replace in flymake
Date: Tue, 8 Feb 2022 15:30:34 +0000	[thread overview]
Message-ID: <CALDnm50HEum6sMD-ywnAxd1uR1N=TnpS0HPHtO151nX2nNFpZw@mail.gmail.com> (raw)
In-Reply-To: <87h7995rd6.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]

On Tue, Feb 8, 2022 at 3:07 PM Robert Pluim <rpluim@gmail.com> wrote:

> >>>>> On Tue, 8 Feb 2022 14:09:34 +0000, João Távora <joaotavora@gmail.com>
> said:
>
>     João> Well, technically, I did "show the patch" even though I didn't
> author said
>     João> patch myself. I answered:
>
>     >> It would seem that the right thing to do is to keep 26.1 dep and do
> what
>     João> Guillaume Pasquet suggests:
>     >> "or substitute the `string-replace` call with
> `replace-regexp-in-string`
>     João> to maintain compatibility as I have done here:
>     >>
>     João>
> https://github.com/Etenil/flymake/commit/9f5f76907b1c258645f65728dd71e7cacffe6d22
>
>     João> Anyway, all good now, just bring the Emacs dep down to 26.1.
> Thanks.
>
> Just so weʼre all clear, we want this in emacs-28 (on top of Lars's
> change to use `replace-regexp-in-string'?
>

I think so. We're in that phase of the release cycle where everything in
emacs-28 that
fixes a bug ends up in main, right?  If so I would say yes. But let Eli or
Lars confirm.

João

[-- Attachment #2: Type: text/html, Size: 1725 bytes --]

  reply	other threads:[~2022-02-08 15:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07 16:11 bug#53853: [PATCH] Don't use string-replace in flymake Brian Leung
2022-02-07 17:32 ` Robert Pluim
2022-02-08  2:17   ` Brian Leung
2022-02-08  6:16     ` Lars Ingebrigtsen
2022-02-08  8:21       ` Robert Pluim
2022-02-08  8:28         ` Brian Leung
2022-02-08  8:35           ` Robert Pluim
2022-02-08  9:20             ` João Távora
2022-02-08  9:50               ` Robert Pluim
2022-02-08  9:54                 ` João Távora
2022-02-08  9:58                   ` João Távora
2022-02-08 13:03                     ` Eli Zaretskii
2022-02-08 13:18                       ` João Távora
2022-02-08 13:54                         ` Eli Zaretskii
2022-02-08 14:09                           ` João Távora
2022-02-08 15:07                             ` Robert Pluim
2022-02-08 15:30                               ` João Távora [this message]
2022-02-08 15:47                                 ` Robert Pluim
2022-02-08 15:51                                   ` João Távora
2022-02-08 16:02                                     ` Robert Pluim
2022-02-08 16:43                                       ` João Távora
2022-02-08 17:02                                         ` Robert Pluim
2022-02-08 17:55                                         ` Dmitry Gutov
2022-02-08 17:08                                 ` Dmitry Gutov
2022-02-09  8:55                                   ` Robert Pluim
2022-02-08  9:52         ` João Távora
2022-02-08 10:19           ` Robert Pluim

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='CALDnm50HEum6sMD-ywnAxd1uR1N=TnpS0HPHtO151nX2nNFpZw@mail.gmail.com' \
    --to=joaotavora@gmail.com \
    --cc=53853@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=leungbk@posteo.net \
    --cc=rpluim@gmail.com \
    /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).