unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Welsh Duggan <mwd@md5i.com>
Cc: 56332@debbugs.gnu.org
Subject: bug#56332: 29.0.50; Large gnus imap groups; articles incorrectly marked as read (old)
Date: Mon, 04 Jul 2022 12:49:25 +0200	[thread overview]
Message-ID: <87mtdp885m.fsf@gnus.org> (raw)
In-Reply-To: <87o7y62qt5.fsf@md5i.com> (Michael Welsh Duggan's message of "Sun, 03 Jul 2022 10:50:46 -0400")

Michael Welsh Duggan <mwd@md5i.com> writes:

> As expected, I cannot cause a failure using this.

Thanks for testing.

> Though I will note that there is no guarantee that a server will send
> its untagged fetch responses in any particular order.

That's true, but I think it's highly unlikely that any servers would do
that, so it doesn't seem worth adding code to sort the headers.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-07-04 10:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01  6:47 bug#56332: 29.0.50; Large gnus imap groups; articles incorrectly marked as read (old) Michael Welsh Duggan
2022-07-01  9:36 ` Lars Ingebrigtsen
2022-07-01  9:50   ` Lars Ingebrigtsen
2022-07-01 15:54     ` Michael Welsh Duggan
2022-07-01 15:56       ` Michael Welsh Duggan
2022-07-02 12:00       ` Lars Ingebrigtsen
2022-07-02 14:30         ` Michael Welsh Duggan
2022-07-02 15:23           ` Lars Ingebrigtsen
2022-07-02 16:00             ` Michael Welsh Duggan
2022-07-02 16:40               ` Michael Welsh Duggan
2022-07-03 10:59                 ` Lars Ingebrigtsen
2022-07-03 14:50                   ` Michael Welsh Duggan
2022-07-04 10:49                     ` Lars Ingebrigtsen [this message]
2022-07-01 15:56   ` Michael Welsh Duggan

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=87mtdp885m.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=56332@debbugs.gnu.org \
    --cc=mwd@md5i.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).