From: john at keeping.me.uk (John Keeping)
Subject: cache issue
Date: Tue, 3 Mar 2015 23:43:42 +0000 [thread overview]
Message-ID: <20150303234342.GS890@serenity.lan> (raw)
In-Reply-To: <CAHmME9q8Lxpitq=4nvmYs9fJ4vHi-ufobdm9mz2HN-BGCUSzEw@mail.gmail.com>
On Tue, Mar 03, 2015 at 11:56:11PM +0100, Jason A. Donenfeld wrote:
> Thanks! Merged. It would be nice to see a test case built out of the
> example you gave in the commit message.
It has to run for a couple of minutes to get sensible results. I guess
we could introduce an EXPENSIVE prerequisite in the same way Git does,
but I'm not sure how often anyone would run the test suite with that
turned on.
prev parent reply other threads:[~2015-03-03 23:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-23 14:06 beber
2015-02-28 12:06 ` bertrand
2015-02-28 12:37 ` john
2015-03-01 18:43 ` bertrand
2015-03-01 19:36 ` john
2015-03-03 9:31 ` john
2015-03-03 15:40 ` Jason
2015-03-03 19:22 ` john
2015-03-03 22:56 ` Jason
2015-03-03 23:43 ` john [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=20150303234342.GS890@serenity.lan \
--to=cgit@lists.zx2c4.com \
/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).