All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bryan O'Sullivan <bos@serpentine.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Greg Kroah-Hartman <greg@kroah.com>,
	linux-kernel@vger.kernel.org,
	viro@parcelfarce.linux.theplanet.co.uk,
	linux-raid@vger.kernel.org
Subject: Re: [PATCH] klibc update
Date: Tue, 16 Mar 2004 12:11:05 -0800	[thread overview]
Message-ID: <1079467865.14516.56.camel@serpentine.pathscale.com> (raw)
In-Reply-To: <20040316115340.361f2a14.akpm@osdl.org>

On Tue, 2004-03-16 at 11:53, Andrew Morton wrote:

> It would be rather handy if someone could maintain the definitive tree for
> this work for a while, until we linusify it.

I'll spend a bit of time in the next few days bringing it up to date
w.r.t the current kernel and klibc trees.

> I don't have a feeling for its stability/readiness/desirability/anthingelse
> at this stage.  How mergeable is it?

Not very.  klibc itself works OK, and the in-tree tools that use it work
OK, but they get very few "pick ourselves up off the ground and do a
complete boot" test cycles.

It's definitely 2.7 material.

	<b


  parent reply	other threads:[~2004-03-16 20:11 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
2004-03-16 19:53             ` Andrew Morton
2004-03-16 20:02               ` Jeff Garzik
2004-03-16 20:11               ` Bryan O'Sullivan [this message]
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=1079467865.14516.56.camel@serpentine.pathscale.com \
    --to=bos@serpentine.com \
    --cc=akpm@osdl.org \
    --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 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.