From: Jeff Garzik <jgarzik@pobox.com>
To: Greg KH <greg@kroah.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
viro@parcelfarce.linux.theplanet.co.uk, bos@serpentine.com,
linux-raid@vger.kernel.org
Subject: Re: [PATCH] klibc update
Date: Tue, 16 Mar 2004 14:32:01 -0500 [thread overview]
Message-ID: <40575631.1080006@pobox.com> (raw)
In-Reply-To: <20040316192458.GB21172@kroah.com>
Greg KH wrote:
> On Tue, Mar 16, 2004 at 02:16:09PM -0500, Jeff Garzik wrote:
>
>>Bryan O'Sullivan and Greg KH at varying times in the past had BK trees,
>>but I didn't know of any up-to-date one.
>
>
> I think Bryan was trying to keep his bk tree up to date with the klibc
> cvs tree, but don't know how well that went.
The latest I found from bos was 2.6.0-test9, not terribly ancient but
still required some hand-fixing of merge conflicts.
>>Note that it isn't my intention to become klibc maintainer... just in
>>case anybody started getting ideas... :)
>
>
> I thought hpa was the klibc maintainer, you're just offering a patch to
> add it to the build :)
Right... I meant I am not going to become the maintainer of said
patch/BK tree :)
Jeff
next prev parent reply other threads:[~2004-03-16 19:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 7:46 [PATCH] klibc update Jeff Garzik
2004-03-16 8:52 ` Andrew Morton
2004-03-16 15:37 ` Greg KH
2004-03-16 19:10 ` Andrew Morton
2004-03-16 19:16 ` Jeff Garzik
2004-03-16 19:24 ` Greg KH
2004-03-16 19:32 ` Jeff Garzik [this message]
2004-03-16 19:53 ` Andrew Morton
2004-03-16 20:02 ` Jeff Garzik
2004-03-16 20:11 ` Bryan O'Sullivan
2004-03-16 20:19 ` Sam Ravnborg
2004-03-16 16:34 ` Jeff Garzik
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=40575631.1080006@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=bos@serpentine.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--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 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.