From: Vincent Bernat <bernat@free.fr>
To: Andrew Morton <akpm@zip.com.au>
Cc: Linus Torvalds <torvalds@transmeta.com>,
lkml <linux-kernel@vger.kernel.org>,
noflushd-devel@lists.sourceforge.net, sct@redhat.com
Subject: Re: [patch 4/12] tunable ext3 commit interval
Date: Sun, 11 Aug 2002 12:15:38 +0200 [thread overview]
Message-ID: <m3u1m1itv9.fsf@neo.loria> (raw)
In-Reply-To: <3D5464CF.DCD510D6@zip.com.au> (Andrew Morton's message of "Fri, 09 Aug 2002 17:56:47 -0700")
OoO En cette nuit striée d'éclairs du samedi 10 août 2002, vers 02:56,
Andrew Morton <akpm@zip.com.au> disait:
> The patch from Stephen Tweedie allows users to modify the journal
> commit interval for the ext3 filesystem.
Could this patch be officially backported to 2.4 to allow the use of
the flexible commit interval in noflushd ?
next prev parent reply other threads:[~2002-08-11 10:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-10 0:56 [patch 4/12] tunable ext3 commit interval Andrew Morton
2002-08-11 10:15 ` Vincent Bernat [this message]
2002-08-11 10:30 ` Andrew Morton
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=m3u1m1itv9.fsf@neo.loria \
--to=bernat@free.fr \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=noflushd-devel@lists.sourceforge.net \
--cc=sct@redhat.com \
--cc=torvalds@transmeta.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