From: "H. Peter Anvin" <hpa@zytor.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.17-rc3-mm1
Date: Mon, 01 May 2006 14:35:45 -0700 [thread overview]
Message-ID: <44567F31.9000302@zytor.com> (raw)
In-Reply-To: <20060501212919.GA21191@mars.ravnborg.org>
Sam Ravnborg wrote:
> On Mon, May 01, 2006 at 11:57:33AM -0700, H. Peter Anvin wrote:
>
>> If it makes your life easier I'd be happy to produce a klibc tree on
>> top of the header cleanup tree.
> klibc is independent today and I really suggest to leave it so until
> header cleanup tree has been merged.
> Otherwise we would end up in a situation where klibc are ready but due
> to dependency on header cleanup we had to wait until 2.6.19.
>
I should have been more clear. I have no intention of abandoning the independent klibc
kernel tree, however, I could easily produce a separate tree with the header cleanup merged.
-hpa
next prev parent reply other threads:[~2006-05-01 21:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 8:47 2.6.17-rc3-mm1 Andrew Morton
2006-05-01 12:54 ` 2.6.17-rc3-mm1 Josh Boyer
2006-05-01 16:59 ` 2.6.17-rc3-mm1 Andrew Morton
2006-05-01 17:33 ` 2.6.17-rc3-mm1 Josh Boyer
2006-05-01 18:57 ` 2.6.17-rc3-mm1 H. Peter Anvin
2006-05-01 21:29 ` 2.6.17-rc3-mm1 Sam Ravnborg
2006-05-01 21:35 ` H. Peter Anvin [this message]
2006-05-01 17:10 ` pi-futex-patchset-v4.patch (was 2.6.17-rc3-mm1 Valdis.Kletnieks
2006-05-03 9:11 ` 2.6.17-rc3-mm1 Benoit Boissinot
2006-05-03 13:48 ` 2.6.17-rc3-mm1 Andrew Morton
2006-05-03 14:15 ` 2.6.17-rc3-mm1 Thomas Gleixner
[not found] ` <20060503144318.GA5505@ens-lyon.fr>
2006-05-05 15:05 ` 2.6.17-rc3-mm1 Benoit Boissinot
2006-05-06 10:30 ` 2.6.17-rc3-mm1 Thomas Gleixner
2006-05-08 17:48 ` 2.6.17-rc3-mm1 john stultz
2006-05-12 11:41 ` 2.6.17-rc3-mm1 Benoit Boissinot
2006-05-12 17:22 ` 2.6.17-rc3-mm1 john stultz
2006-05-09 12:40 ` 2.6.17-rc3-mm1 Benoit Boissinot
2006-05-12 7:25 ` 2.6.17-rc3-mm1 J.A. Magallón
2006-05-12 7:40 ` 2.6.17-rc3-mm1 Andrew Morton
2006-05-12 7:47 ` 2.6.17-rc3-mm1 J.A. Magallón
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=44567F31.9000302@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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.