From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Newsgroups: gmane.emacs.bugs Subject: bug#53853: [PATCH] Don't use string-replace in flymake Date: Tue, 8 Feb 2022 15:51:59 +0000 Message-ID: References: <87r18e7fb7.fsf@gmail.com> <87zgn1ublj.fsf@gnus.org> <87mtj17oqg.fsf@gmail.com> <87ee4d7o3f.fsf@gmail.com> <875ypp7kmu.fsf@gmail.com> <83iltpwlwn.fsf@gnu.org> <83fsotwjiw.fsf@gnu.org> <87h7995rd6.fsf@gmail.com> <87czjx5pip.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000004cf07805d783b0f6" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34113"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Brian Leung , Lars Ingebrigtsen , 53853@debbugs.gnu.org To: Robert Pluim Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Feb 08 19:32:24 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nHVHs-0008kW-Dy for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 08 Feb 2022 19:32:24 +0100 Original-Received: from localhost ([::1]:46166 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nHVHp-00060u-RP for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 08 Feb 2022 13:32:21 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:51468) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nHSmh-0007aA-KJ for bug-gnu-emacs@gnu.org; Tue, 08 Feb 2022 10:52:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:54484) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nHSmg-0004ya-9d for bug-gnu-emacs@gnu.org; Tue, 08 Feb 2022 10:52:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nHSmg-0007fs-8a for bug-gnu-emacs@gnu.org; Tue, 08 Feb 2022 10:52:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 08 Feb 2022 15:52:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 53853 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 53853-submit@debbugs.gnu.org id=B53853.164433549129460 (code B ref 53853); Tue, 08 Feb 2022 15:52:02 +0000 Original-Received: (at 53853) by debbugs.gnu.org; 8 Feb 2022 15:51:31 +0000 Original-Received: from localhost ([127.0.0.1]:48380 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nHSmB-0007f5-8n for submit@debbugs.gnu.org; Tue, 08 Feb 2022 10:51:31 -0500 Original-Received: from mail-oo1-f44.google.com ([209.85.161.44]:34663) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nHSm9-0007es-3R for 53853@debbugs.gnu.org; Tue, 08 Feb 2022 10:51:29 -0500 Original-Received: by mail-oo1-f44.google.com with SMTP id k13-20020a4a948d000000b003172f2f6bdfso12689014ooi.1 for <53853@debbugs.gnu.org>; Tue, 08 Feb 2022 07:51:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=e3E/zYHaHwU2XpEDSH7vYMLcSQ51aR3MMtvKu+gsN+Q=; b=IPu3Wkrv2KrxcQXRBHLkHZVZ77HXKhGY4FWGyWHL/kiQAuXEoRMxpJFuwcva0xuXka xzOVbYGrozTGpT4aG07OgKsg+MhJs9lgA47/EZIRlbLwNZhJRyCFYjVoYGQnUv4KsSrV 2EKvs+bGWf9rOeUusU16PHbzOHXRqTQU5y2R7hpqYTp3QVtY3YbtPRPkA+Ly/M+0Id/d 3xNbzlU1c95izDbGiQ7SVQnBrQLiXEfxh11mm8NQQeRpScG2lafb/AcD+6Ja+E+pA3MR 1S2hHQuKPGpuqYy1J4UXtUI6m1yE2nVVNhHmlIWSCnA0A16fsnQjcZC/c8leI63jmcLG trGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=e3E/zYHaHwU2XpEDSH7vYMLcSQ51aR3MMtvKu+gsN+Q=; b=Gg+esJ5gvUu/NA4mXgJFn9yelH3W3kIJ/1qayHPbecBYZI8mIt5y2U71usfd8e6vE9 +ULIPSscpuRGsD+Q826y4Ojg2j/B0glGh533yBHrT52a7yY4j7StuujfoeHDIo/Np/hF 36HD3ck8S/tHXrT+UFCXvH5Y6iLEjWYbSZQ7bfH95hNW3ZQGGPO6raLZuI0zyPpcqe4b E+Q0bch3gQzhvssQpAhTJcCcu+kPMjAdcUqQmymH+xVjdHm1DM7S1xsmUejQ0aCrCv9T cHahRZurr7PFA8nDvN6O9/bg0WD3QQ9i3SmtMM7CQTZvcQpg6WsV/Kjm0jLuvPViaf/L rAPw== X-Gm-Message-State: AOAM532fQ7coFH8f3v155YOGWV9gZY1El7NdzZ7JMb9oAzQOFOQxtMhD OKbWpTM/ys1wnmuuxsLozdVpSOnuyv1/x0w0xCY= X-Google-Smtp-Source: ABdhPJxmCiGnwHQaGQFWa3w7SW3rR1/EKAXr/0LlK8YyjfuNkyeLyy6UC/VPoX5S179+rQC4HUzxK7FFnppnQn8E6gc= X-Received: by 2002:a05:6870:e350:: with SMTP id a16mr553624oae.143.1644335482071; Tue, 08 Feb 2022 07:51:22 -0800 (PST) In-Reply-To: <87czjx5pip.fsf@gmail.com> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:226397 Archived-At: --0000000000004cf07805d783b0f6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Feb 8, 2022 at 3:47 PM Robert Pluim wrote: > Jo=C3=A3o> I think so. We're in that phase of the release cycle where > everything in > Jo=C3=A3o> emacs-28 that > Jo=C3=A3o> fixes a bug ends up in main, right? If so I would say yes= . But > let Eli or > Jo=C3=A3o> Lars confirm. > > Everything that gets committed to the release branch always gets > merged to master, unless it=CA=BCs marked 'do not merge'. Right that's what I meant by "ends up in main" ("main" the new name of the former "master" branch, which is still accessible by that name AFAIK). > The phase of the > release cycle we=CA=BCre in is: doc fixes and regressions only (unless we > manage to bribe Lars/Eli somehow :-) ) Right. And isn't this a regression? Something that used to work in Emacs 27.1 and doesn't in the upcoming Emacs 28.1? Anyway, committing to master/main is probably fine too, because that's what governs the "emission" of an ELPA package, as far as I know. Jo=C3=A3o --0000000000004cf07805d783b0f6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Tue, Feb 8, 2022 at 3:47 PM Robert Pluim <rpluim@gmail.com> wrote:
=C2=A0 =C2=A0 Jo=C3=A3o> I think so. We're in that phase of the rele= ase cycle where everything in
=C2=A0 =C2=A0 Jo=C3=A3o> emacs-28 that
=C2=A0 =C2=A0 Jo=C3=A3o> fixes a bug ends up in main, right?=C2=A0 If so= I would say yes. But let Eli or
=C2=A0 =C2=A0 Jo=C3=A3o> Lars confirm.

Everything that gets committed to the release branch always gets
merged to master, unless it=CA=BCs marked 'do not merge'.

Right that's what I meant by "ends up in m= ain" ("main" the new name of the
former "= ;master" branch, which is still accessible by that name AFAIK).
=C2=A0
The p= hase of the
release cycle we=CA=BCre in is: doc fixes and regressions only (unless we manage to bribe Lars/Eli somehow :-) )

Right.=C2=A0 And isn't this a regression?=C2=A0 Something that used t= o work in Emacs 27.1
and doesn't in the upcoming Emacs 2= 8.1?

Anyway, committing to master/main is probably= fine too, because that's what
governs the "emission&quo= t; of an ELPA package, as far as I know.

Jo=C3=A3o=
--0000000000004cf07805d783b0f6--