unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: "João Távora" <joaotavora@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, 08 Feb 2022 17:02:31 +0100	[thread overview]
Message-ID: <878rul5otk.fsf@gmail.com> (raw)
In-Reply-To: <CALDnm50_s3m0rxoEHwfnjiAOuxFJdEnH+Ed_vJZNVXoEihXc7w@mail.gmail.com> ("João Távora"'s message of "Tue, 8 Feb 2022 15:51:59 +0000")

>>>>> 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
-- 





  reply	other threads:[~2022-02-08 16:02 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
2022-02-08 15:47                                 ` Robert Pluim
2022-02-08 15:51                                   ` João Távora
2022-02-08 16:02                                     ` Robert Pluim [this message]
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=878rul5otk.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=53853@debbugs.gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=larsi@gnus.org \
    --cc=leungbk@posteo.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 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).