All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: mtd <linux-mtd@lists.infradead.org>
Subject: Re: Inode corrupted after CVS update
Date: Tue, 08 Apr 2003 10:47:49 +0200	[thread overview]
Message-ID: <3E928CB5.5010306@imc-berlin.de> (raw)
In-Reply-To: 1049791383.18045.144.camel@passion.cambridge.redhat.com

David Woodhouse schrieb:
> On Tue, 2003-04-08 at 09:33, Steven Scholz wrote:
> 
>>So how stable is the MTD/JFFS2 code anyway?
>>Is the CVS the only place for me to get the source?
>>Or are there some offical, release patches?
> 
> 
> The jffs2-2_4-branch from CVS, which is in Marcelo's latest 2.4.21-pre,
> is the one that's _really_ intended to be stable -- but that's because
> we don't make any exciting changes there at all.

But the performance improvements lately done on the JFFS2 code is in 
there!?

So for production systems I should patch my 2.4.20 with the 
jffs2-2_4-branch !?

> If you want to track -HEAD it's worth keeping an eye on the IRC channel
> -- if Thomas and I are spending the day discussing how best to fix
> stuff, and there's a lot of swearing and debugging going on, then it's
> probably not a good time to update :)
:o))

Thanks,

Steven

  reply	other threads:[~2003-04-08  8:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-08  7:19 Inode corrupted after CVS update Steven Scholz
2003-04-08  8:21 ` David Woodhouse
2003-04-08  8:33   ` Steven Scholz
2003-04-08  8:43     ` David Woodhouse
2003-04-08  8:47       ` Steven Scholz [this message]
2003-04-08  9:08         ` David Woodhouse

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=3E928CB5.5010306@imc-berlin.de \
    --to=steven.scholz@imc-berlin.de \
    --cc=linux-mtd@lists.infradead.org \
    /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.