From: Dave Abrahams <dave@boostpro.com>
To: Michael Welsh Duggan <mwd@cert.org>
Cc: Katsumi Yamaoka <yamaoka@jpl.org>,
ding@gnus.org, Julien Danjou <julien@danjou.info>
Subject: Re: [gnus git] branch master updated: m0-5-97-gafdb0e3 =6= Revert "Add recent argument to nnimap-find-article-by-message-id" ; Fix for macos keychain access ; gnus-try-warping-via-registry: [bugfix] don't act as though you've found the article when you haven't ; gnus-request-head: when gnus-override-method is set, allow the backend `request-head' function to determine the group name on its own. ; Change gnus-set-difference from O(N^2) to O(N) ; Filter out negative article numbers during expiry
Date: Fri, 31 Aug 2012 22:08:44 -0700 [thread overview]
Message-ID: <m27gsee3dv.fsf@boostpro.com> (raw)
In-Reply-To: <tntbohrgmex.fsf@waterbuck.yellow.cert.org> (Michael Welsh Duggan's message of "Fri, 31 Aug 2012 10:34:46 -0400")
on Fri Aug 31 2012, Michael Welsh Duggan <mwd-AT-cert.org> wrote:
> I really hope that the reverted commit can be fixed and re-added at some
> point. It is an important speed-up (minutes to seconds!) on systems
> that have miserable search by message-id times (stupid MS Exchange).
>
> Only reverting this change means that the
> nnimap-find-article-by-message-id call in nnimap-request-move-article
> has too many arguments.
Please pull again; it should be back now.
--
Dave Abrahams
BoostPro Computing Software Development Training
http://www.boostpro.com Clang/LLVM/EDG Compilers C++ Boost
next prev parent reply other threads:[~2012-09-01 5:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1T6mSl-00057h-3s@quimby.gnus.org>
2012-08-29 21:23 ` Julien Danjou
2012-08-31 4:38 ` Katsumi Yamaoka
2012-08-31 6:36 ` Dave Abrahams
2012-08-31 14:34 ` Michael Welsh Duggan
2012-09-01 5:08 ` Dave Abrahams [this message]
2012-09-01 5:08 ` Dave Abrahams
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=m27gsee3dv.fsf@boostpro.com \
--to=dave@boostpro.com \
--cc=ding@gnus.org \
--cc=julien@danjou.info \
--cc=mwd@cert.org \
--cc=yamaoka@jpl.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).