From: Sam Ravnborg <sam@ravnborg.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
greg@kroah.com, 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 21:19:17 +0100 [thread overview]
Message-ID: <20040316201917.GB2396@mars.ravnborg.org> (raw)
In-Reply-To: <20040316115340.361f2a14.akpm@osdl.org>
On Tue, Mar 16, 2004 at 11:53:40AM -0800, Andrew Morton wrote:
> Jeff Garzik <jgarzik@pobox.com> wrote:
> >
> > >>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 :)
>
> It would be rather handy if someone could maintain the definitive tree for
> this work for a while, until we linusify it.
>
> I don't have a feeling for its stability/readiness/desirability/anthingelse
> at this stage. How mergeable is it?
I need to dig through the build system once more.
Last time I did it, I only managed to get it to the 'working' stage.
Not at the 'good enough' stage.
This minor issue should not delay the inclusion though - just a
note that something needs to be looked at in this area.
Sam
next prev parent reply other threads:[~2004-03-16 20:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 7:46 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
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 [this message]
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=20040316201917.GB2396@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@osdl.org \
--cc=bos@serpentine.com \
--cc=greg@kroah.com \
--cc=jgarzik@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®