From: Stefan Kangas <stefankangas@gmail.com>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>, 42184@debbugs.gnu.org
Cc: bzg@gnu.org, egh@e6h.org
Subject: bug#42184: 27.0.91; org-fontify-whole-heading-line does not work in emacs 27
Date: Sun, 6 Sep 2020 15:06:26 +0000 [thread overview]
Message-ID: <CADwFkmnq=SCq46S0Q1uj4dmHPH0HHVkMZpdHOUyUNKEZkDGj9w@mail.gmail.com> (raw)
In-Reply-To: <87wo17f13a.fsf@gmail.com>
Kévin Le Gouguec <kevin.legouguec@gmail.com> writes:
> Speaking of Org's maint branch (where the fix has been applied), are
> there plans to synchronize it with the emacs-27 branch, so that Emacs
> 27.2 benefits from all the fixes to the 9.3 release?
If the maint branch contains only bug fixes, why shouldn't we?
Eli will explain what he prefers, but I would propose to open a new bug
report to track it, and we can mark it as blocking for the Emacs 27.2
release. That way there is less risk of forgetting about it when it's
time to make the next point release.
next prev parent reply other threads:[~2020-09-06 15:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-04 2:29 bug#42184: 27.0.91; org-fontify-whole-heading-line does not work in emacs 27 Erik Hetzner
2020-07-04 17:13 ` Kévin Le Gouguec
2020-07-04 17:18 ` Eli Zaretskii
2020-07-04 17:50 ` Kévin Le Gouguec
2020-07-04 19:52 ` Kévin Le Gouguec
2020-07-05 2:30 ` Eli Zaretskii
2020-07-05 8:57 ` Kévin Le Gouguec
2020-07-05 14:58 ` Eli Zaretskii
2020-07-05 16:02 ` Kévin Le Gouguec
2020-07-05 16:21 ` Eli Zaretskii
2020-07-08 11:50 ` Kévin Le Gouguec
2020-07-09 14:16 ` Kévin Le Gouguec
2020-08-06 4:10 ` Kyle Meyer
2020-08-06 9:32 ` Kévin Le Gouguec
2020-08-06 13:35 ` Eli Zaretskii
2020-09-06 8:12 ` Bastien
2020-09-06 14:10 ` Kévin Le Gouguec
2020-09-06 15:06 ` Stefan Kangas [this message]
2020-09-06 14:19 ` Kyle Meyer
2020-09-06 15:06 ` Stefan Kangas
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='CADwFkmnq=SCq46S0Q1uj4dmHPH0HHVkMZpdHOUyUNKEZkDGj9w@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=42184@debbugs.gnu.org \
--cc=bzg@gnu.org \
--cc=egh@e6h.org \
--cc=kevin.legouguec@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).