From: Daniel Phillips <phillips@bonn-fries.net>
To: Andreas Dilger <adilger@turbolinux.com>,
Ext2 development mailing list <ext2-devel@lists.sourceforge.net>,
Linux kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [Ext2-devel] [PATCH] update ext2 documentation
Date: Fri, 20 Apr 2001 14:07:34 +0200 [thread overview]
Message-ID: <01042014132609.01958@subspace.radio> (raw)
In-Reply-To: <200104201016.f3KAGwct030395@webber.adilger.int>
In-Reply-To: <200104201016.f3KAGwct030395@webber.adilger.int>
On Fri, 20 Apr 2001, Andreas Dilger wrote:
> The included patch updates Documentation/filesystems/ext2 to reflect
> current information about ext2. It also adds some more information
> that people have told me is hard to find in other places (such as a
> description of the superblock compatibility flags, file and filesystem
> size limits).
To quote Oliver Twist: "Please, Sir, I want some more". How about a
explanation of the significance of GOOD_OLD_REV, etc. In particular, I'm
curious why CURRENT_REV is defined as GOOD_OLD_REV and not DYNAMIC_REV.
--
Daniel
next prev parent reply other threads:[~2001-04-20 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-20 10:16 [PATCH] update ext2 documentation Andreas Dilger
2001-04-20 12:07 ` Daniel Phillips [this message]
2001-04-20 18:25 ` [Ext2-devel] " Andreas Dilger
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=01042014132609.01958@subspace.radio \
--to=phillips@bonn-fries.net \
--cc=adilger@turbolinux.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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