From: Eli Zaretskii <eliz@gnu.org>
To: Konstantin Kharlamov <Hi-Angel@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: nxml comments fix (was: Start of Emacs 30 release cycle)
Date: Mon, 01 Jul 2024 16:41:45 +0300 [thread overview]
Message-ID: <86y16ldyau.fsf@gnu.org> (raw)
In-Reply-To: <ca735ef3f0ee25acc00a98b6cc0a9f9c6cfb5d1f.camel@yandex.ru> (message from Konstantin Kharlamov on Mon, 01 Jul 2024 16:15:57 +0300)
> From: Konstantin Kharlamov <Hi-Angel@yandex.ru>
> Date: Mon, 01 Jul 2024 16:15:57 +0300
>
> On Sun, 2024-06-23 at 16:44 +0300, Eli Zaretskii wrote:
> > I hope to make the first pretest of Emacs 30.1 in about a month from
> > now.
>
> Hello! As it's soon the pretest time, I'd just like to point out a
> simple nxml-mode bugfix that would be nice to have in Emacs 30
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=71772 (the 1-st patch out
> of the two).
Thanks, but there's no reason to cross-post bugs here. All the
relevant people read the bug list all the time, so your bug report was
noticed and will not be forgotten.
next prev parent reply other threads:[~2024-07-01 13:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 13:44 Start of Emacs 30 release cycle Eli Zaretskii
2024-06-24 8:32 ` Stephen Berman
2024-06-24 12:47 ` Eli Zaretskii
2024-06-24 13:49 ` Stephen Berman
2024-06-24 15:05 ` Eli Zaretskii
2024-06-25 10:41 ` Stephen Berman
2024-06-25 13:48 ` Eli Zaretskii
2024-06-26 6:45 ` Stephen Berman
2024-06-25 14:10 ` Robert Pluim
2024-06-25 14:48 ` Stephen Berman
2024-06-25 15:09 ` Robert Pluim
2024-06-25 15:57 ` Eli Zaretskii
2024-06-26 6:53 ` Stephen Berman
2024-06-26 9:27 ` Robert Pluim
2024-07-01 13:15 ` nxml comments fix (was: Start of Emacs 30 release cycle) Konstantin Kharlamov
2024-07-01 13:41 ` Eli Zaretskii [this message]
2024-07-01 14:00 ` Konstantin Kharlamov
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=86y16ldyau.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Hi-Angel@yandex.ru \
--cc=emacs-devel@gnu.org \
/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).