From: Matthew Wilcox <Matthew.Wilcox@genedata.com>
To: Hannu Martikka <martikka@stybba.ntc.nokia.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Pa-risc Linux timetables?
Date: Thu, 5 Aug 1999 15:32:48 +0200 [thread overview]
Message-ID: <19990805153248.S11586@mencheca.ch.genedata.com> (raw)
In-Reply-To: <Pine.HPX.4.05.9908051545080.18930-100000@gamgee.ntc.nokia.com>; from Hannu Martikka on Thu, Aug 05, 1999 at 03:54:09PM +0300
On Thu, Aug 05, 1999 at 03:54:09PM +0300, Hannu Martikka wrote:
> Do we have any estimate on parisc/linux timetables? When is the pa-risc
> Linux going to be "released"? Do we target it to 2.5 or 2.6?
>
> We are now based on 2.2.1. How big effort would be required to merge
> pa-risc linux (2.2.1) to 2.3/2.4?
I believe we're aiming at having a 2.2 version ready for the end of the
year -- approximately the same time as Linus expects to have a 2.4 release
out. Updating to 2.4 shouldn't be a big problem, and we don't have to be
ready for the release of 2.4.0 -- Linus merged alpha, sparc, ppc and mips
trees at several stages after 2.2.0 was released. (Indeed, there is a
big mips merge in the 2.2.11 prepatches.)
Don't worry about 2.4 yet :-)
--
Matthew Wilcox <willy@bofh.ai>
"Windows and MacOS are products, contrived by engineers in the service of
specific companies. Unix, by contrast, is not so much a product as it is a
painstakingly compiled oral history of the hacker subculture." - N Stephenson
next prev parent reply other threads:[~1999-08-05 13:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-03 9:40 [parisc-linux] unsatisfied symbols Ingo Matthaes
1999-08-03 13:43 ` Steven A. DuChene
1999-08-03 13:48 ` Philipp Rumpf
1999-08-03 22:32 ` Helge Deller
1999-08-04 11:28 ` Ingo Matthaes
1999-08-05 12:54 ` [parisc-linux] Pa-risc Linux timetables? Hannu Martikka
1999-08-05 13:32 ` Matthew Wilcox [this message]
1999-08-05 13:48 ` Alex deVries
1999-08-05 13:48 ` Philipp Rumpf
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=19990805153248.S11586@mencheca.ch.genedata.com \
--to=matthew.wilcox@genedata.com \
--cc=martikka@stybba.ntc.nokia.com \
--cc=parisc-linux@thepuffingroup.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