From: Andi Kleen <ak@muc.de>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Patch(2.5.54): devfs shrink - integration candidate
Date: 06 Jan 2003 05:56:22 +0100 [thread overview]
Message-ID: <m3d6naq3k9.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <20030105203725.A10808@adam.yggdrasil.com>
"Adam J. Richter" <adam@yggdrasil.com> writes:
>
> Finally, I'd like to move forward toward getting this into
> Linus's kernel. Any blessings, curses, requests for changes or advice
> on the best way to proceed would be appreciated.
Me thinks you're two to three months too late for 2.5. This looks definitely not like
a good idea to merge in a feature/code freeze, when the main goal should be to
finally get 2.6 out. Submit it when 2.7 opens.
-Andi
next prev parent reply other threads:[~2003-01-06 4:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030105201413.A10685@adam.yggdrasil.com>
2003-01-06 4:37 ` Patch(2.5.54): devfs shrink - integration candidate Adam J. Richter
2003-01-06 4:56 ` Andi Kleen [this message]
2003-01-06 9:57 ` Andrew Walrond
2003-01-06 10:12 ` John Bradford
2003-01-06 5:04 ` Andrew Morton
2003-01-08 18:55 ` H. Peter Anvin
2003-01-06 5:14 Adam J. Richter
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=m3d6naq3k9.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=adam@yggdrasil.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.