[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#53853: [PATCH] Don't use string-replace in flymake
From: |
Robert Pluim |
Subject: |
bug#53853: [PATCH] Don't use string-replace in flymake |
Date: |
Tue, 08 Feb 2022 17:02:31 +0100 |
>>>>> On Tue, 8 Feb 2022 15:51:59 +0000, João Távora <joaotavora@gmail.com>
>>>>> said:
João> On Tue, Feb 8, 2022 at 3:47 PM Robert Pluim <rpluim@gmail.com> wrote:
João> I think so. We're in that phase of the release cycle where
>> everything in
João> emacs-28 that
João> fixes a bug ends up in main, right? If so I would say yes. But
>> let Eli or
João> Lars confirm.
>>
>> Everything that gets committed to the release branch always gets
>> merged to master, unless itʼs marked 'do not merge'.
João> Right that's what I meant by "ends up in main" ("main" the new name
of the
João> former "master" branch, which is still accessible by that name AFAIK).
In GNU Elpa maybe. In emacs the branch is called 'master'.
>> The phase of the
>> release cycle weʼre in is: doc fixes and regressions only (unless we
>> manage to bribe Lars/Eli somehow :-) )
João> Right. And isn't this a regression? Something that used to work in
Emacs
João> 27.1
João> and doesn't in the upcoming Emacs 28.1?
João> Anyway, committing to master/main is probably fine too, because
that's what
João> governs the "emission" of an ELPA package, as far as I know.
Yes, but the emacs-28 -> master merge happens pretty regularly as
well. Iʼm assuming thereʼs some magic that then makes GNU Elpa take notice.
Robert
--
- bug#53853: [PATCH] Don't use string-replace in flymake, (continued)
- bug#53853: [PATCH] Don't use string-replace in flymake, João Távora, 2022/02/08
- bug#53853: [PATCH] Don't use string-replace in flymake, João Távora, 2022/02/08
- bug#53853: [PATCH] Don't use string-replace in flymake, Eli Zaretskii, 2022/02/08
- bug#53853: [PATCH] Don't use string-replace in flymake, João Távora, 2022/02/08
- bug#53853: [PATCH] Don't use string-replace in flymake, Eli Zaretskii, 2022/02/08
- bug#53853: [PATCH] Don't use string-replace in flymake, João Távora, 2022/02/08
- bug#53853: [PATCH] Don't use string-replace in flymake, Robert Pluim, 2022/02/08
- bug#53853: [PATCH] Don't use string-replace in flymake, João Távora, 2022/02/08
- bug#53853: [PATCH] Don't use string-replace in flymake, Robert Pluim, 2022/02/08
- bug#53853: [PATCH] Don't use string-replace in flymake, João Távora, 2022/02/08
- bug#53853: [PATCH] Don't use string-replace in flymake,
Robert Pluim <=
- bug#53853: [PATCH] Don't use string-replace in flymake, João Távora, 2022/02/08
- bug#53853: [PATCH] Don't use string-replace in flymake, Robert Pluim, 2022/02/08
- bug#53853: [PATCH] Don't use string-replace in flymake, Dmitry Gutov, 2022/02/08
- bug#53853: [PATCH] Don't use string-replace in flymake, Dmitry Gutov, 2022/02/08
- bug#53853: [PATCH] Don't use string-replace in flymake, Robert Pluim, 2022/02/09
- bug#53853: [PATCH] Don't use string-replace in flymake, João Távora, 2022/02/08
- bug#53853: [PATCH] Don't use string-replace in flymake, Robert Pluim, 2022/02/08