From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Getting new mail really slow with nnml marks
Date: Sat, 20 Oct 2001 11:53:50 +0200 [thread overview]
Message-ID: <iluitda63ip.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <y68elo0zl0u.fsf@cutter-john.mit.edu> (David Z Maze's message of "Thu, 18 Oct 2001 17:38:25 -0400")
David Z Maze <dmaze@MIT.EDU> writes:
> Simon Josefsson <jas@extundo.com> writes:
> SJ> If you touch a .marks file, `nnml-marks-changed-p' must return
> SJ> non-nil! New mail shouldn't matter, but iff the .marks file is
> SJ> modified n-m-c-p return non-nil.
>
> *checks* Yup, the patched version works correctly on this front.
I've applied your patch, thank you.
prev parent reply other threads:[~2001-10-20 9:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-17 15:16 David Z Maze
2001-10-17 16:16 ` Simon Josefsson
2001-10-17 16:54 ` David Z Maze
2001-10-17 17:14 ` David Z Maze
2001-10-17 17:28 ` Simon Josefsson
2001-10-17 17:44 ` David Z Maze
2001-10-17 19:54 ` Simon Josefsson
2001-10-17 21:05 ` David Z Maze
2001-10-18 19:34 ` Simon Josefsson
2001-10-18 21:38 ` David Z Maze
2001-10-20 9:53 ` Simon Josefsson [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=iluitda63ip.fsf@barbar.josefsson.org \
--to=jas@extundo.com \
--cc=ding@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.
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 NNTP newsgroup(s).