public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Dave Jones <davej@redhat.com>
Cc: Daniel Pittman <daniel@rimspace.net>,
	linux-kernel@vger.kernel.org, Ext3-users@redhat.com,
	Chris Mason <mason@suse.com>
Subject: Re: mode data=journal in ext3. Is it safe to use?
Date: Thu, 17 Jun 2004 09:55:43 -0700	[thread overview]
Message-ID: <40D1CD0F.4030306@namesys.com> (raw)
In-Reply-To: <20040617100813.GA19280@redhat.com>

Dave Jones wrote:

>On Wed, Jun 16, 2004 at 10:35:50PM -0700, Hans Reiser wrote:
>
> > >the reluctance of the developers to adapt to the 4K kernel stacks in
> > >2.6.recent,
> > >
> > do you use them?  I don't know real users who do, or else I would be 
> > quicker to care.
>
>The Fedora Core 2 kernel (and what will be RHEL4) is currently
>using 4K stacks.  This makes up quite a large userbase.
>  
>
Sigh.  I guess we have to support it then.

Chris, are you up to doing it?

> > On the one hand, you complain about how we were unstable, and on the 
> > other hand you complain about how we aren't willing to destabilize the 
> > code to add new features to what is no longer the development branch.  
> > Seems pretty inconsistent logically to me.
>
>If you really are reluctant it fix it, there's always the option of
>marking CONFIG_REISER4 as dependant on CONFIG_BROKEN if CONFIG_4KSTACKS
>is selected.
>
>		Dave
>
>
>
>  
>


  reply	other threads:[~2004-06-17 16:54 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <40FB8221D224C44393B0549DDB7A5CE83E31B1@tor.lokal.lan>
2004-06-15 18:09 ` mode data=journal in ext3. Is it safe to use? Petter Larsen
2004-06-15 18:20   ` Eugene Crosser
2004-06-17  8:36     ` Petter Larsen
2004-06-16  7:34   ` Oleg Drokin
2004-06-17  8:27     ` Petter Larsen
2004-06-17 17:09       ` Oleg Drokin
2004-06-18  9:41         ` Helge Hafting
2004-06-18 10:15           ` Oleg Drokin
2004-06-18 11:30             ` Paulo Marques
2004-06-18 12:05               ` Oleg Drokin
2004-06-21 17:42                 ` mode data=journal in ext3. Is it safe to use? Conclusion Petter Larsen
2004-06-19 19:16               ` mode data=journal in ext3. Is it safe to use? Bernd Eckenfels
2004-06-16 15:49   ` Timothy Miller
2004-06-17  0:51     ` Daniel Pittman
2004-06-17  3:02       ` Tim Connors
2004-06-17  5:35       ` Hans Reiser
2004-06-17 10:08         ` Dave Jones
2004-06-17 16:55           ` Hans Reiser [this message]
2004-06-17  8:29     ` Petter Larsen
2004-06-17 19:30       ` Daniel Egger
     [not found]       ` <87wu26mto2.fsf@enki.rimspace.net>
2004-06-27 14:17         ` Petter Larsen
2004-06-28  0:22           ` Daniel Pittman
     [not found]     ` <1805.216.148.213.196.1087426691.squirrel@www.code-visions.com>
2004-06-17 11:23       ` Petter Larsen
2004-06-17 16:26         ` Andreas Dilger
2004-06-17 14:56 Ken Ryan
2004-06-17 16:06 ` Timothy Miller
2004-06-17 17:20   ` Hans Reiser
2004-06-17 19:15     ` Ken Ryan
2004-06-18  6:18       ` Hans Reiser
2004-06-17 19:43     ` Daniel Egger
2004-06-17 19:59       ` Ken Ryan
2004-06-19 14:49 ` Petter Larsen

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=40D1CD0F.4030306@namesys.com \
    --to=reiser@namesys.com \
    --cc=Ext3-users@redhat.com \
    --cc=daniel@rimspace.net \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@suse.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