From: khromy@lnuxlab.ath.cx (khromy)
To: linux-kernel@vger.kernel.org
Subject: Re: Announce: XFS split patches for 2.4.20 - respin
Date: Tue, 17 Dec 2002 22:04:50 -0500 [thread overview]
Message-ID: <20021218030450.GA7578@lnuxlab.ath.cx> (raw)
In-Reply-To: <6153.1040177760@kao2.melbourne.sgi.com>
What are the chances of this getting into 2.4 soon?
On Wed, Dec 18, 2002 at 01:16:00PM +1100, Keith Owens wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Content-Type: text/plain; charset=us-ascii
>
> ftp://oss.sgi.com/projects/xfs/download/patches/2.4.20.
>
> The xfs patches for 2.4.20 have been respun as of 2002-12-18 02:00 UTC.
>
> For some time the XFS group have been producing split patches for XFS,
> separating the core XFS changes from additional patches such as kdb,
> xattr, acl, dmapi. The split patches are released to the world with
> the hope that developers and distributors will find them useful.
>
> Read the README in each directory very carefully, the split patch
> format has changed over a few kernel releases. Any questions that are
> covered by the README will be ignored. There is even a 2.4.21/README
> for the terminally impatient :).
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: Exmh version 2.1.1 10/15/1999
>
> iD8DBQE9/9pdi4UHNye0ZOoRAjd7AKCUGoWqZ3SJGRj2d7ssCEsiZb03vwCdFm4J
> 5ymEscu9jY2EEZuwz2NwPK0=
> =0KMC
> -----END PGP SIGNATURE-----
--
L1: khromy ;khromy(at)lnuxlab.ath.cx
next prev parent reply other threads:[~2002-12-18 2:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 2:16 Announce: XFS split patches for 2.4.20 - respin Keith Owens
2002-12-18 3:04 ` khromy [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-14 1:34 Keith Owens
2003-02-05 23:49 Keith Owens
2003-03-19 5:03 Keith Owens
2003-04-07 5:59 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=20021218030450.GA7578@lnuxlab.ath.cx \
--to=khromy@lnuxlab.ath.cx \
--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 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.