From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: linux-kernel@vger.kernel.org, viro@parcelfarce.linux.theplanet.co.uk
Subject: Re: [RFC] must fix lists
Date: Tue, 21 Oct 2003 09:18:27 -0700 [thread overview]
Message-ID: <20031021091827.0c58065e.rddunlap@osdl.org> (raw)
In-Reply-To: <3F94C833.8040204@cyberone.com.au>
On Tue, 21 Oct 2003 15:46:27 +1000 Nick Piggin <piggin@cyberone.com.au> wrote:
| The following people have their names in Documentation/must-fix.txt. Lots
| of others in should-fix.txt in 2.6.0-test8-mm1. Please review your entries.
| Also, please add any other substantial changes you need before 2.6. Thanks.
In the should-fix.txt file:
o viro: cleaning up options-parsers in filesystems. (patch exists, needs
porting).
The parser lib functions are merged and approx. 15 filesystems
have been converted to use it, so this could be changed to:
o viro: convert more filesystems to use lib/parser.c for parsing options
(still PRI2 I suppose)
--
~Randy
next prev parent reply other threads:[~2003-10-21 16:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 5:46 Nick Piggin
2003-10-21 9:36 ` Lars Marowsky-Bree
2003-10-22 0:40 ` Nick Piggin
2003-10-21 16:18 ` Randy.Dunlap [this message]
2003-10-22 2:50 ` Albert Cahalan
2003-10-23 21:11 ` Alan Cox
2003-10-23 21:09 ` Alan Cox
2003-10-23 23:46 ` Nick Piggin
2003-10-24 1:06 ` Albert Cahalan
2003-10-24 1:55 ` viro
2003-10-24 0:23 ` Chris Wright
2003-10-25 20:18 ` Alan Cox
2003-10-27 12:53 ` [RFC][PATCH] " Nick Piggin
2003-10-27 18:24 ` ACPI PM-Timer [Was: Re: [RFC][PATCH] must fix lists] Dominik Brodowski
2003-10-27 18:42 ` john stultz
2003-10-27 18:49 ` Dominik Brodowski
2003-10-27 19:07 ` john stultz
2003-10-27 23:01 ` ACPI PM-Timer rev.2 [Was: Re: ACPI PM-Timer [Was: Re: [RFC][PATCH] must fix lists]] Dominik Brodowski
2003-11-04 22:03 ` john stultz
2003-10-27 9:48 [RFC] must fix lists Mikael Pettersson
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=20031021091827.0c58065e.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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
all inboxes | Powered by JetHome®