public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Kbuild Devel <kbuild-devel@lists.sourceforge.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Announce: Kernel Build for 2.5, Release 2.4 is available
Date: Fri, 17 May 2002 14:07:46 +1000	[thread overview]
Message-ID: <8230.1021608466@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Wed, 15 May 2002 23:20:38 +1000." <22794.1021468838@ocs3.intra.ocs.com.au>

On Wed, 15 May 2002 23:20:38 +1000, 
Keith Owens <kaos@ocs.com.au> wrote:
>On 14 May 2002 20:46:38 -0700, 
>Thomas Duffy <tduffy@directvinternet.com> wrote:
>>I have only tested x86 as of this moment.  If anyone is dying for a
>>clean kbuild-2.5-common-2.4.19-pre8-1, let me know and I can turn those
>>wheels.
>
>I have uploaded common-2.4.18-7 and common-2.5.15-4 to sourceforge.
>http://sourceforge.net/projects/kbuild/, package kbuild-2.5, download
>release 2.4.  This cross syncs the 2.4.18 and 2.5.15 architecture
>independent code, where the two kernels have similar requirements.  I
>will take Tom Duffy's 2.4.19-pre8 patch, add it to common-2.4.18-7 and
>issue common-2.4.19-pre8-1 tomorrow.

kbuild-2.5-common-2.4.19-pre8-1.bz2, kbuild-2.5-i386-2.4.19-pre8-1.bz2
are available.  Use with core-14.

I built these from common-2.4.18-7, i386-2.4.18-2 plus some previous
work on 2.4.19-pre6 then updated to -pre8.  A cross check against Tom
Duffy's 19-pre8 patch found errors in my patches and Tom's, which have
been reconciled.


      reply	other threads:[~2002-05-17  4:08 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-03 14:19 Keith Owens
2002-05-03 14:37 ` your mail tomas szepe
2002-05-03 15:07   ` tomas szepe
2002-05-03 15:29   ` Keith Owens
2002-05-03 15:45     ` tomas szepe
2002-05-03 15:57       ` kbuild 2.5 release 2.4 Keith Owens
2002-05-03 16:41         ` tomas szepe
2002-05-04 10:58           ` tomas szepe
2002-05-04 11:24             ` Keith Owens
2002-05-04 11:26               ` Zwane Mwaikambo
2002-05-04 12:11                 ` Keith Owens
2002-05-04 11:58                   ` Zwane Mwaikambo
2002-05-04 16:21                     ` rddunlap
2002-05-04 11:39               ` tomas szepe
2002-05-04 12:00                 ` Keith Owens
2002-05-04 12:15                   ` tomas szepe
2002-05-04 16:19                     ` rddunlap
2002-05-04 16:29                       ` Tomas Szepe
2002-05-04 16:30                         ` rddunlap
2002-05-05  2:27                       ` Keith Owens
2002-05-04 13:01 ` Announce: Kernel Build for 2.5, Release 2.4 is available Keith Owens
2002-05-06  6:27   ` Keith Owens
2002-05-07 17:47     ` [kbuild-devel] " Thomas Duffy
2002-05-09 11:45   ` Keith Owens
2002-05-10  1:46     ` [kbuild-devel] " Thomas Duffy
2002-05-10  3:21       ` Keith Owens
2002-05-11  9:32   ` Keith Owens
2002-05-14  0:12     ` [kbuild-devel] " Thomas Duffy
2002-05-14  2:44       ` Keith Owens
2002-05-14  5:44     ` Keith Owens
2002-05-15  3:46       ` [kbuild-devel] " Thomas Duffy
2002-05-15 13:20         ` Keith Owens
2002-05-17  4:07           ` Keith Owens [this message]

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=8230.1021608466@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox