linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: Linus Torvalds <torvalds@osdl.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [TRIVIAL] use ext2/ext3 consistently in Kconfig
Date: 27 Jul 2003 12:05:28 +0100	[thread overview]
Message-ID: <1059303927.12758.10.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030726195722.GB16160@louise.pinerecords.com>

On Sad, 2003-07-26 at 20:57, Tomas Szepe wrote:
> $subj + also clarify what fs versions the current reiser module supports.
> Patch against -bk3.          


> This is the journaling version of the Second extended file system
-         (often called ext3), the de facto standard Linux file system
+         (often called ext2), the de facto standard Linux file system
          (method to organize files on a storage device) for hard disks.

It is called ext3 not ext2. This change is dubious (actually the big
problem is it is totally unclear what we are discussing the name of.
How about

  Ext3 is the journalling versions of the second extended file system
(ext2). Ext2 was the former de-facto standard Linux file system. Ext3
uses the same on disk layout but with a journal.
 ...


  parent reply	other threads:[~2003-07-27 10:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-26 19:57 [TRIVIAL] use ext2/ext3 consistently in Kconfig Tomas Szepe
2003-07-26 20:21 ` Jeff Sipek
2003-07-26 20:28   ` Sean Neakums
2003-07-26 21:21     ` Tomas Szepe
2003-07-26 21:30       ` Sean Neakums
2003-07-26 21:40         ` Tomas Szepe
2003-07-26 20:52   ` Kurt Wall
2003-07-26 21:01     ` Sean Neakums
2003-07-27 11:05 ` Alan Cox [this message]
2003-07-27 11:23   ` Tomas Szepe
2003-07-27 13:59   ` Hans Reiser
2003-08-05  7:29 Tomas Szepe

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=1059303927.12758.10.camel@dhcp22.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=szepe@pinerecords.com \
    --cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).