From: Nick Piggin <piggin@cyberone.com.au>
To: Lars Marowsky-Bree <lmb@suse.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] must fix lists
Date: Wed, 22 Oct 2003 10:40:18 +1000 [thread overview]
Message-ID: <3F95D1F2.1080304@cyberone.com.au> (raw)
In-Reply-To: <20031021093601.GH26189@marowsky-bree.de>
Lars Marowsky-Bree wrote:
>On 2003-10-21T15:46:27,
> Nick Piggin <piggin@cyberone.com.au> said:
>
>The multipath module will be (outcome of KS) implemented as a
>device-mapper personality, which Sistina / Joe are developing. So,
>luckily, I'm sort of out of the loop of the "must fix" list, but I'll
>hopefully have some of the issues on my "will fix" list anyway ;-)
>
OK so that means it can go in any time really, right? So it can
be removed from the list. Thanks.
next prev parent reply other threads:[~2003-10-22 0:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 5:46 [RFC] must fix lists Nick Piggin
2003-10-21 9:36 ` Lars Marowsky-Bree
2003-10-22 0:40 ` Nick Piggin [this message]
2003-10-21 16:18 ` Randy.Dunlap
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
-- strict thread matches above, loose matches on Subject: below --
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=3F95D1F2.1080304@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@suse.de \
/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