From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Michael Welsh Duggan <mwd@md5i.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Andreas Schwab <schwab@linux-m68k.org>,
53352-done@debbugs.gnu.org
Subject: bug#53352: 29.0.50; IMAP INBOX not refreshing using `gnus-group-get-new-news'
Date: Mon, 31 Jan 2022 11:27:44 -0800 [thread overview]
Message-ID: <87r18niu33.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <8735l4gemt.fsf@md5i.com> (Michael Welsh Duggan's message of "Mon, 31 Jan 2022 09:32:10 -0500")
On 01/31/22 09:32 AM, Michael Welsh Duggan wrote:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Michael Welsh Duggan <mwd@md5i.com> writes:
>>
>>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>>
>>>> On 01/24/22 19:31 PM, Lars Ingebrigtsen wrote:
>>>>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>>>>
>>>>>> I suppose the Emacs 28 ship has sailed? It would be nice to include this
>>>>>> fix in the release.
>>>>>
>>>>> It's a regression from 27.2, so including a fix in Emacs 28 would be
>>>>> appropriate (if it's simple enough). But we can run it on master for a
>>>>> while before backporting.
>>>>
>>>> Okay, good. I'm attaching the patch I'm using right now -- this appears
>>>> to fix it. I'll give it another day or two.
>>>
>>> I can confirm that this solves the problem for me, at least for some
>>> simple local testing. I'll run with this patch applied for a few days
>>> as well.
>>
>> Great, thank you! I'll aim to push on say Thursday, then we can let it
>> simmer on master for a bit, then backport to 28.
>
> Just a ping to make sure this didn't get forgotten.
Not forgotten! But it was languishing in my local rebase pile, just
pushed.
I'm going to close this now, but please reopen if anything seems not to
be working as it should.
Eric
next prev parent reply other threads:[~2022-01-31 19:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 23:07 bug#53352: 29.0.50; IMAP INBOX not refreshing using `gnus-group-get-new-news' Michael Welsh Duggan
2022-01-21 10:29 ` Lars Ingebrigtsen
2022-01-22 16:25 ` Michael Welsh Duggan
2022-01-23 12:58 ` Lars Ingebrigtsen
2022-01-23 16:55 ` Michael Welsh Duggan
2022-01-24 9:18 ` Lars Ingebrigtsen
2022-01-24 16:15 ` Michael Welsh Duggan
2022-01-24 16:33 ` Lars Ingebrigtsen
2022-01-24 16:34 ` Andreas Schwab
2022-01-24 17:59 ` Eric Abrahamsen
2022-01-24 18:06 ` Michael Welsh Duggan
2022-01-24 18:48 ` Eric Abrahamsen
2022-01-24 18:31 ` Lars Ingebrigtsen
2022-01-24 19:20 ` Eric Abrahamsen
2022-01-24 21:15 ` Michael Welsh Duggan
2022-01-24 22:18 ` Eric Abrahamsen
2022-01-31 14:32 ` Michael Welsh Duggan
2022-01-31 19:27 ` Eric Abrahamsen [this message]
2022-02-07 10:49 ` Andreas Schwab
2022-02-07 16:50 ` Eric Abrahamsen
2022-02-07 17:42 ` Andreas Schwab
2022-02-07 21:17 ` Eric Abrahamsen
2022-02-07 21:34 ` Andreas Schwab
2022-02-07 23:51 ` Eric Abrahamsen
2022-02-09 4:38 ` Eric Abrahamsen
2022-02-09 8:45 ` Andreas Schwab
2022-02-10 19:38 ` Eric Abrahamsen
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=87r18niu33.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=53352-done@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mwd@md5i.com \
--cc=schwab@linux-m68k.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).