From: Robert Pluim <rpluim@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 38011@debbugs.gnu.org
Subject: bug#38011: 27.0.50; [PATCH] WIP on allowing Gnus backends to return header data directly
Date: Mon, 18 Jan 2021 11:48:34 +0100 [thread overview]
Message-ID: <87bldmwmf1.fsf@gmail.com> (raw)
In-Reply-To: <87wnwc88ej.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sat, 16 Jan 2021 21:00:36 -0800")
>>>>> On Sat, 16 Jan 2021 21:00:36 -0800, Eric Abrahamsen <eric@ericabrahamsen.net> said:
Eric> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>> On 01/05/21 09:47 AM, Lars Ingebrigtsen wrote:
>>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>>
>>>> Morally the same: the agent has its own `gnus-agent-uncached-articles'
>>>> function, which consults the .agentview file, so it uses that instead of
>>>> `gnus-sorted-difference'. But the same idea.
>>>
>>> Right.
Eric> [...]
>> Anyway, I'll keep looking at this patch for a bit, and see if I can find
>> any more problems with it.
Eric> I found a couple more, in agent file writing, and have pushed a commit
Eric> fixing that. So far as I can tell this now works as intended. I've run
Eric> side-by-side comparisons of master and this feature branch, messing with
Eric> the cache and the agent, and feel fairly confident that behavior is the
Eric> same in terms of header fetching, and files written to disk. I think I'd
Eric> feel okay merging this, but would also be happy to let it mellow longer.
I think previous experience shows that the only way to find bugs in
this kind of code is to foist it on us :-)
Robert
next prev parent reply other threads:[~2021-01-18 10:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 21:34 bug#38011: 27.0.50; [PATCH] WIP on allowing Gnus backends to return header data directly Eric Abrahamsen
2019-11-01 14:12 ` Lars Ingebrigtsen
2019-11-01 18:41 ` Eric Abrahamsen
2019-11-01 20:52 ` Eric Abrahamsen
2019-11-02 14:49 ` Lars Ingebrigtsen
2019-11-07 23:21 ` Eric Abrahamsen
2019-11-08 21:03 ` Lars Ingebrigtsen
2019-11-08 21:43 ` Eric Abrahamsen
2019-11-08 21:58 ` Lars Ingebrigtsen
2020-03-29 19:50 ` Eric Abrahamsen
2020-04-30 4:50 ` Lars Ingebrigtsen
2020-09-27 4:13 ` Eric Abrahamsen
2020-09-27 12:16 ` Lars Ingebrigtsen
2020-09-27 23:41 ` Eric Abrahamsen
2021-01-02 3:18 ` Eric Abrahamsen
2021-01-02 5:59 ` Lars Ingebrigtsen
2021-01-02 20:49 ` Eric Abrahamsen
2021-01-03 7:45 ` Lars Ingebrigtsen
2021-01-03 19:53 ` Eric Abrahamsen
2021-01-04 9:05 ` Lars Ingebrigtsen
2021-01-04 18:09 ` Eric Abrahamsen
2021-01-05 8:47 ` Lars Ingebrigtsen
2021-01-05 17:02 ` Eric Abrahamsen
2021-01-17 5:00 ` Eric Abrahamsen
2021-01-18 10:48 ` Robert Pluim [this message]
2021-01-18 21:12 ` Eric Abrahamsen
2021-01-18 16:37 ` Lars Ingebrigtsen
2021-01-03 19:54 ` Eric Abrahamsen
2021-01-03 21: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=87bldmwmf1.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=38011@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=larsi@gnus.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).