From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Semyonov <daniel@dsemy.com>
Cc: 71888@debbugs.gnu.org
Subject: bug#71888: [PATCH] nnfeed: (Mostly) fix group descriptions
Date: Sat, 06 Jul 2024 13:12:08 +0300 [thread overview]
Message-ID: <86r0c64yo7.fsf@gnu.org> (raw)
In-Reply-To: <87v81njynu.fsf@dsemy.com> (message from Daniel Semyonov on Wed, 03 Jul 2024 00:01:57 +0300)
> From: Daniel Semyonov <daniel@dsemy.com>
> Cc: 71888@debbugs.gnu.org
> Date: Wed, 03 Jul 2024 00:01:57 +0300
>
> >>>>> Eli Zaretskii writes:
>
> >> Date: Tue, 02 Jul 2024 02:43:29 +0300
> >> From: Daniel Semyonov via "Bug reports for GNU Emacs,
> >> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> >>
> >> I realized a few days ago I barely tested group descriptions in nnatom
> >> (and by extension nnfeed), and turns out they were in fact broken.
> >> Attached is a patch which should fix them.
>
> > Thanks, but please tell whether this is for the emacs-30 release
> > branch or for master. IOW, does the problem exist on emacs-30 or only
> > on master?
>
> Sorry, this problem exists on both emacs-30 and on master (it was
> unfortunately broken since nnfeed and nnatom were added to Emacs last
> year).
Thanks, so I've now installed the patch on the emacs-30 release
branch.
> I'm currently going over nnfeed and nnatom when I have free time to
> hopefully find any issues I missed before Emacs 30 is released (as it
> will be the first stable release to include them).
So I'm not yet closing this bug, given that you say there's more to be
done here.
Thanks.
prev parent reply other threads:[~2024-07-06 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 23:43 bug#71888: [PATCH] nnfeed: (Mostly) fix group descriptions Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-02 12:11 ` Eli Zaretskii
2024-07-02 21:01 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-06 10:12 ` Eli Zaretskii [this message]
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=86r0c64yo7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71888@debbugs.gnu.org \
--cc=daniel@dsemy.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).