All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: rob@landley.net
Cc: Erik Andersen <andersen@codepoet.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Will uclibc be supported in 2.6? (was Re: [PATCH] Re: [PATCH] scsi.h uses "u8" which isn't defined.)
Date: Tue, 19 Aug 2003 17:47:06 -0400	[thread overview]
Message-ID: <3F429ADA.1050402@pobox.com> (raw)
In-Reply-To: <200308191738.36574.rob@landley.net>

Rob Landley wrote:
> I'm all for doing it in 2.7.  I just want to know what I should do for 2.6.  
> If there's a consensus that we're talking about 2.7 and allowing ad-hockery 
> to continue in 2.6, I'll shut up. :)


That's always been the consensus :)

2.6 is long past the point for major header surgery and breakage.

	Jeff




  reply	other threads:[~2003-08-19 21:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <lRjc.6o4.3@gated-at.bofh.it>
     [not found] ` <lRjg.6o4.15@gated-at.bofh.it>
     [not found]   ` <lWLS.39x.5@gated-at.bofh.it>
     [not found]     ` <lWLZ.39x.29@gated-at.bofh.it>
2003-08-18 18:54       ` [PATCH] Re: [PATCH] scsi.h uses "u8" which isn't defined Ihar 'Philips' Filipau
2003-08-18 19:04         ` Jeff Garzik
2003-08-19 12:32           ` Rob Landley
2003-08-19 17:26             ` Jeff Garzik
2003-08-19 21:38               ` Will uclibc be supported in 2.6? (was Re: [PATCH] Re: [PATCH] scsi.h uses "u8" which isn't defined.) Rob Landley
2003-08-19 21:47                 ` Jeff Garzik [this message]
2003-08-20  1:42               ` [PATCH] Re: [PATCH] scsi.h uses "u8" which isn't defined Erik Andersen
2003-08-20 23:48             ` Jamie Lokier
2003-08-21  0:02               ` Jeff Garzik
2003-08-22  0:32                 ` Rob Landley
2003-08-22  0:50                   ` Chris Friesen
2003-08-22  1:58                     ` Rob Landley
2003-08-22  0:54                   ` Jeff Garzik
2003-08-18 20:40         ` Sam Ravnborg

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=3F429ADA.1050402@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=andersen@codepoet.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    /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.