From: Wakko Warner <wakko@animx.eu.org>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Thought about delayed sync
Date: Sun, 9 Oct 2011 07:56:39 -0400 [thread overview]
Message-ID: <20111009115639.GA25344@animx.eu.org> (raw)
In-Reply-To: <20111009093641.4cfa79c9@notabene.brown>
NeilBrown wrote:
> I think you are suggesting this:
>
> http://neil.brown.name/blog/20110216044002#5
You hit the nail on the head. Yes.
> Patches welcome :-)
I'd love to, but unfortunately, this is way beyond my capabilities.
--
Microsoft has beaten Volkswagen's world record. Volkswagen only created 22
million bugs.
prev parent reply other threads:[~2011-10-09 11:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-08 18:03 Thought about delayed sync Wakko Warner
2011-10-08 22:00 ` Thomas Fjellstrom
2011-10-09 12:04 ` Wakko Warner
2011-10-09 12:34 ` Thomas Fjellstrom
2011-10-09 13:44 ` Wakko Warner
2011-10-08 22:36 ` NeilBrown
2011-10-09 11:32 ` Alexander Kühn
2011-10-09 22:12 ` NeilBrown
2011-10-09 11:56 ` Wakko Warner [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=20111009115639.GA25344@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).