From: Keith Owens <kaos@ocs.com.au>
To: Thomas Duffy <tduffy@directvinternet.com>
Cc: Kbuild Devel <kbuild-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [kbuild-devel] Re: Announce: Kernel Build for 2.5, release 3.0 is available
Date: Thu, 13 Jun 2002 10:15:31 +1000 [thread overview]
Message-ID: <30954.1023927331@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "12 Jun 2002 13:55:44 MST." <1023915345.23246.20.camel@tduffy-lnx.afara.com>
On 12 Jun 2002 13:55:44 -0700,
Thomas Duffy <tduffy@directvinternet.com> wrote:
>On Wed, 2002-06-12 at 06:54, Keith Owens wrote:
>
>> New files:
>>
>> kbuild-2.5-core-19
>
>> kbuild-2.5-i386-2.4.18-4
>> kbuild-2.5-i386-2.4.19-pre10-2
>
>> kbuild-2.5-common-2.5.21-1
>> kbuild-2.5-i386-2.5.21-1
>
>hrm. I don't see any of these on the sourceforge site...
I got side tracked and did not complete the upload. They are there
now.
prev parent reply other threads:[~2002-06-13 0:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 2:35 Announce: Kernel Build for 2.5, release 3.0 is available Keith Owens
2002-06-03 5:31 ` Keith Owens
2002-06-03 19:22 ` [kbuild-devel] " Thomas Duffy
2002-06-03 19:31 ` Thunder from the hill
2002-06-03 19:58 ` Thomas Duffy
2002-06-03 20:06 ` Thunder from the hill
2002-06-03 21:12 ` Thomas Duffy
2002-06-04 0:19 ` Keith Owens
2002-06-04 0:29 ` Thomas Duffy
2002-06-04 4:53 ` Keith Owens
2002-06-04 9:16 ` Alex Riesen
2002-06-04 22:55 ` Keith Owens
2002-06-05 2:25 ` [kbuild-devel] " John Cowan
2002-06-05 2:38 ` Keith Owens
2002-06-05 18:13 ` Mark Mielke
2002-06-05 13:19 ` Alex Riesen
2002-06-04 13:59 ` [kbuild-devel] " Arnd Bergmann
2002-06-05 13:53 ` Keith Owens
2002-06-07 8:49 ` Keith Owens
2002-06-12 13:54 ` Keith Owens
2002-06-12 20:55 ` [kbuild-devel] " Thomas Duffy
2002-06-13 0:15 ` 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=30954.1023927331@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tduffy@directvinternet.com \
/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