public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Ben Collins <bcollins@debian.org>
Cc: kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Announce: Kernel Build for 2.5, Release 1.11 is available
Date: Mon, 17 Dec 2001 16:54:53 +1100	[thread overview]
Message-ID: <5132.1008568493@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 17 Dec 2001 00:28:12 CDT." <20011217002812.A377@blimpo.internal.net>

On Mon, 17 Dec 2001 00:28:12 -0500, 
Ben Collins <bcollins@debian.org> wrote:
>If anyone needs them, I can provide a small diff for the sparc/sparc64
>Vger CVS changes to apply on top of the main kbuild-2.5 patch. Very
>minor change (hint, in Vger, netlink is compiled unconditionally now).

Since they are small, mail them to linux-{kernel,kbuild} and maybe the
sparc lists as well.


  reply	other threads:[~2001-12-17  5:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-17  5:04 Announce: Kernel Build for 2.5, Release 1.11 is available Keith Owens
2001-12-17  5:28 ` Ben Collins
2001-12-17  5:54   ` Keith Owens [this message]
2001-12-17  6:26     ` Ben Collins
2001-12-18  5:12 ` Keith Owens

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=5132.1008568493@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=bcollins@debian.org \
    --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