From: Lars Ingebrigtsen <larsi@gnus.org>
To: Sam Steingold <sds@gnu.org>
Cc: 55834@debbugs.gnu.org
Subject: bug#55834: 29.0.50; gnus: Z n in digest group does not catch up
Date: Mon, 11 Jul 2022 13:21:01 +0200 [thread overview]
Message-ID: <87ilo3x5cy.fsf@gnus.org> (raw)
In-Reply-To: <lz8rq69dln.fsf@3c22fb11fdab.ant.amazon.com> (Sam Steingold's message of "Thu, 09 Jun 2022 09:21:40 -0400")
Sam Steingold <sds@gnu.org> writes:
> At any rate, arguing about it is counterproductive.
> No is no, let us move on.
OK; closing this bug report, then.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-07-11 11:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 16:05 bug#55834: 29.0.50; gnus: Z n in digest group does not catch up Sam Steingold
2022-06-07 17:11 ` Lars Ingebrigtsen
2022-06-08 15:26 ` Sam Steingold
2022-06-09 10:33 ` Lars Ingebrigtsen
2022-06-09 13:21 ` Sam Steingold
2022-07-11 11:21 ` Lars Ingebrigtsen [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=87ilo3x5cy.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=55834@debbugs.gnu.org \
--cc=sds@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).