From: Andrew Morton <akpm@digeo.com>
To: Szakacsits Szabolcs <szaka@sienet.hu>
Cc: aebr@win.tue.nl, linux-fsdevel@vger.kernel.org,
ext2-devel@lists.sourceforge.net
Subject: Re: handling unrecognised mount options
Date: Sun, 16 Mar 2003 20:34:20 -0800 [thread overview]
Message-ID: <20030316203420.797ad47f.akpm@digeo.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0303170416190.27925-100000@divine.city.tvnet.hu>
Szakacsits Szabolcs <szaka@sienet.hu> wrote:
>
> Another issue is predictibility. If one gives an option he expects the
> driver to behave just like that. Long time convention.
>
OK, I'll buy that one.
Now what about the inability to switch between kernels?
next prev parent reply other threads:[~2003-03-17 4:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-16 11:00 handling unrecognised mount options Andrew Morton
2003-03-16 11:50 ` Andries Brouwer
2003-03-16 19:04 ` Randy.Dunlap
2003-03-16 22:46 ` Andrew Morton
2003-03-17 4:25 ` Szakacsits Szabolcs
2003-03-17 4:34 ` Andrew Morton [this message]
2003-03-17 5:23 ` Szakacsits Szabolcs
2003-03-17 5:32 ` Andrew Morton
2003-03-17 9:18 ` Andries Brouwer
2003-03-17 16:54 ` Bryan Henderson
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=20030316203420.797ad47f.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=aebr@win.tue.nl \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=szaka@sienet.hu \
/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