All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Shawn Starr <spstarr@sh0n.net>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
	Andreas Dilger <adilger@clusterfs.com>,
	Con Kolivas <conman@kolivas.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [BENCHMARK] EXT3 vs EXT2 results with rmap14a and testing with  contest 0.34
Date: Mon, 23 Sep 2002 13:05:50 -0700	[thread overview]
Message-ID: <3D8F741E.578D49C4@digeo.com> (raw)
In-Reply-To: 200209231600.03978.spstarr@sh0n.net

Shawn Starr wrote:
> 
> On September 23, 2002 03:03 pm, Stephen C. Tweedie wrote:
> > Hi,
> >
> > On Wed, Sep 18, 2002 at 11:32:19PM -0700, Andrew Morton wrote:
> > > I had a little patch.  Stephen is working on the big fix.
> >
> > It passed an overnight Cerberus at the end of last week.  :-)
> > Checking into CVS shortly, then I need to set up a pile of recovery
> > tests to make sure it's still writing everything it needs to in time.
> >
>
> Which branch of the kernel is this going into? an -ac branch or 2.5 bk?
> 

The way it usually goes is that Stephen checks it into ext3 CVS (based
off current Marcelo kernel) and I port it up to 2.5.

  reply	other threads:[~2002-09-23 20:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-19  1:18 EXT3 Testing w/ rmap14a with contest results Shawn Starr
2002-09-19  3:10 ` Andrew Morton
2002-09-19  2:16   ` Shawn Starr
     [not found] ` <200209182140.30364.spstarr@sh0n.net>
     [not found]   ` <1032403983.3d893c0f8986b@kolivas.net>
2002-09-19  4:16     ` [BENCHMARK] EXT3 vs EXT2 results with rmap14a and testing with contest 0.34 Shawn Starr
2002-09-19  4:21       ` Shawn Starr
2002-09-19  6:13       ` Andreas Dilger
2002-09-19  5:44         ` Shawn Starr
2002-09-19  6:32         ` Andrew Morton
2002-09-23 19:03           ` Stephen C. Tweedie
2002-09-23 20:00             ` Shawn Starr
2002-09-23 20:05               ` Andrew Morton [this message]
2002-09-23 20:22               ` Stephen C. Tweedie

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=3D8F741E.578D49C4@digeo.com \
    --to=akpm@digeo.com \
    --cc=adilger@clusterfs.com \
    --cc=conman@kolivas.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.com \
    --cc=spstarr@sh0n.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.