From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: James Bourne <jbourne@hardrock.org>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.21-uv1 patch released
Date: Fri, 13 Jun 2003 15:55:37 -0600 [thread overview]
Message-ID: <209030000.1055541336@caspian.scsiguy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0306131542570.24382-100000@cafe.hardrock.org>
> Thanks. I've turned the 20030603.tar.gz file into a patch and added it to
> the updates patch I host to allow people a single point to download errata
> for the 2.4.21 kernel.
>
> Unfortunately I have never used BK nor have I any intention at this point,
> so I hope the tar ball will reflect the same information. I have included a
> pointer to the SRC directory for people to follow as well.
I would just like Marcelo to take the BK version if/when he incorperates
a newer drop into his BK tree.
--
Justin
prev parent reply other threads:[~2003-06-13 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 18:37 2.4.21-uv1 patch released James Bourne
2003-06-13 18:42 ` Randy.Dunlap
2003-06-13 18:49 ` James Bourne
2003-06-13 19:32 ` Justin T. Gibbs
2003-06-13 21:49 ` James Bourne
2003-06-13 21:55 ` Justin T. Gibbs [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=209030000.1055541336@caspian.scsiguy.com \
--to=gibbs@scsiguy.com \
--cc=jbourne@hardrock.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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;
as well as URLs for NNTP newsgroup(s).