All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: MTD List <linux-mtd@lists.infradead.org>
Subject: Re: [RFD] Move 2.4 code out from CVS head
Date: Fri, 04 Mar 2005 07:53:54 +0000	[thread overview]
Message-ID: <1109922835.29792.106.camel@baythorne.infradead.org> (raw)
In-Reply-To: <42280EB6.4030007@imc-berlin.de>

On Fri, 2005-03-04 at 08:31 +0100, Steven Scholz wrote:
> How about SUMMARY patch then? ;-)

$DEITY no. The 2.4 branch doesn't even have the mount time improvements
from a couple of years ago. It isn't having summary support.

> And BTW: How do I get the 2.4 branch from CVS?

cvs up -r jffs2-2_4-branch

Or just look at Marcelo's current kernel. Most of what I've done
recently (i.e. in the last year or so) to fix JFFS2 bugs in 2.4 has been
in linux/fs/inode.c, not in linux/fs/jffs2/

-- 
dwmw2

  reply	other threads:[~2005-03-04  7:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-03  9:14 [RFD] Move 2.4 code out from CVS head Thomas Gleixner
2005-03-03 10:28 ` David Woodhouse
2005-03-03 10:44   ` Thomas Gleixner
2005-03-03 10:46     ` David Woodhouse
2005-03-03 10:53       ` Thomas Gleixner
2005-03-03 11:00         ` David Woodhouse
2005-03-03 11:03           ` Thomas Gleixner
2005-03-03 11:05             ` David Woodhouse
2005-03-03 11:29           ` Steven Scholz
2005-03-03 11:38             ` Thomas Gleixner
2005-03-03 11:41             ` David Woodhouse
2005-03-03 16:48             ` Nicolas Pitre
2005-03-03 18:20               ` David Woodhouse
2005-03-04  7:31                 ` Steven Scholz
2005-03-04  7:53                   ` David Woodhouse [this message]
2005-03-04  9:00                   ` Thomas Gleixner
2005-03-04 11:01                   ` Artem B. Bityuckiy

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=1109922835.29792.106.camel@baythorne.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=steven.scholz@imc-berlin.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 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.