From: Anuradha Ratnaweera <anuradha@gnu.org>
To: James Davies <james_m_davies@yahoo.com>
Cc: Wayne.Brown@altec.com, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.0
Date: Sun, 25 Nov 2001 13:31:57 +0600 [thread overview]
Message-ID: <20011125133157.A2190@bee.lk> (raw)
In-Reply-To: <86256B0F.0026CFDE.00@smtpnotes.altec.com> <20011125071857Z280740-17408+19611@vger.kernel.org>
In-Reply-To: <20011125071857Z280740-17408+19611@vger.kernel.org>; from james_m_davies@yahoo.com on Sun, Nov 25, 2001 at 05:14:53PM +1000
On Sun, Nov 25, 2001 at 05:14:53PM +1000, James Davies wrote:
> On Sun, 25 Nov 2001 16:52, Wayne.Brown@altec.com wrote:
> > Is there going to be an "official" patch from 2.4.15 to 2.5.0? I'd rather
> > not ftp the whole kernel tarball over a modem connection, and I don't have
> > the disk space on my laptop to keep both the complete 2.4 and 2.5 source at
> > the same time anyway.
>
> 2.4.15 is the same as 2.5.0
I think he is concerned about the _official_ 2.4.15 and the _official_ 2.5.0,
because, subsequent patches for 2.5.0 will not _cleanly_ apply on 2.4.15 tree
(although fixing them should be extremely trivial).
Can somebody confirm that the difference is only the version numbers in the
Makefile, and no other changes in Documentation/ etc?
Cheers,
Anuradha
--
Debian GNU/Linux (kernel 2.4.13)
The human animal differs from the lesser primates in his passion for
lists of "Ten Best".
-- H. Allen Smith
next prev parent reply other threads:[~2001-11-25 7:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-25 6:52 Linux 2.5.0 Wayne.Brown
2001-11-25 7:14 ` James Davies
2001-11-25 7:31 ` Anuradha Ratnaweera [this message]
2001-11-25 7:53 ` Arnaldo Carvalho de Melo
2001-11-25 7:23 ` Arnaldo Carvalho de Melo
-- strict thread matches above, loose matches on Subject: below --
2001-11-25 15:16 Wayne.Brown
2001-11-25 16:51 ` Arnaldo Carvalho de Melo
2001-11-25 21:28 Wayne.Brown
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=20011125133157.A2190@bee.lk \
--to=anuradha@gnu.org \
--cc=Wayne.Brown@altec.com \
--cc=james_m_davies@yahoo.com \
--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