From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: What happened to snappy low-bandwidth nnimap?
Date: Wed, 05 Sep 2012 00:09:55 +0200 [thread overview]
Message-ID: <87mx15l9sc.fsf@gnus.org> (raw)
In-Reply-To: <87fw7xrzld.fsf@dod.no> (Steinar Bang's message of "Wed, 08 Aug 2012 20:46:38 +0200")
Steinar Bang <sb@dod.no> writes:
> I guess it would be neat if one of you could use git bisect to find the
> commit that triggered the behaviour...?
It was introduced with the "nonexist" handling, I think.
It's a major problem, but the thing is that I've so far been unable to
reproduce it myself, so fixing it has been kinda... er... difficult.
--
(domestic pets only, the antidote for overdose, milk.)
http://lars.ingebrigtsen.no * Sent from my Emacs
next prev parent reply other threads:[~2012-09-04 22:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 18:47 David Engster
2012-08-08 15:41 ` Richard Riley
2012-08-08 18:46 ` Steinar Bang
2012-08-08 20:00 ` David Engster
2012-08-08 20:21 ` Michael Welsh Duggan
2012-08-08 20:36 ` David Engster
2012-08-09 20:26 ` David Engster
2012-09-04 22:09 ` Lars Ingebrigtsen [this message]
2012-08-08 20:03 ` 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=87mx15l9sc.fsf@gnus.org \
--to=larsi@gnus.org \
--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).