From: Nick Piggin <piggin@cyberone.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] must fix list
Date: Wed, 24 Sep 2003 23:12:53 +1000 [thread overview]
Message-ID: <3F719855.5010703@cyberone.com.au> (raw)
In-Reply-To: <20030916234746.0612ec90.akpm@osdl.org>
Andrew Morton wrote:
>Nick Piggin <piggin@cyberone.com.au> wrote:
>
>> I don't know what happened to this, but I thought it was quite good.
>> Maybe I missed something?
>>
>
>It just didn't seem very relevant: people weren't keeping me up to date and
>a lot of the patches which were going in weren't related to anything on the
>lists.
>
I liked it. I think it gives you a good idea of the bigger changes
that need to happen and who is doing what. It might be a good idea to
keep around when you want to impose some sort of code freeze.
>
>> Anyway I have removed AS from the list because it is done. I removed CFQ
>> as well because when the schedulers become runtime selectable (sometime
>> I hope), merging it becomes a non issue, even during the stable series I
>> think.
>>
>> I updated the kernel/sched.c section a bit.
>>
>> I moved 64-bit dev_t from should fix to must fix.
>>
>> It looks like quite a bit can be struck off, but I'll leave it up to those
>> who actually did the work.
>>
>
>Thanks. Just for you, I'll do an update.
>
Hows it going?
>
>> Maybe these should go in Documentation/must-fix/ to make patching and
>> syncing easier?
>>
>
>maybe...
>
>
IMO it would help
prev parent reply other threads:[~2003-09-24 13:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 5:14 [PATCH] must fix list Nick Piggin
2003-09-17 6:47 ` Andrew Morton
2003-09-24 13:12 ` Nick Piggin [this message]
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=3F719855.5010703@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@osdl.org \
--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