From: Alex deVries <adevries@thepuffingroup.com>
To: Hannu Martikka <martikka@stybba.ntc.nokia.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Pa-risc Linux timetables?
Date: Thu, 05 Aug 1999 09:48:49 -0400 [thread overview]
Message-ID: <37A99641.EDD7A44@thepuffingroup.com> (raw)
In-Reply-To: Pine.HPX.4.05.9908051545080.18930-100000@gamgee.ntc.nokia.com
Hannu Martikka wrote:
> I just noticed that Linus is doing feature freeze for 2.4 in few weeks.
> That raised couple of questions.
I've talked to Linus about merging the changes into his mainstream
kernel tree, and he's agreed, but only once our kernel actually does
something. I agree with this.
> 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?
It's very difficult to suggest a timeline to a project that's done only
on volunteer time, so I don't think anyone's ready to commit to a
schedule.
My feeling is we'll address the kernel merge once we have a kernel to
merge. A LOT of the architecture ports had their own seperate tree for
many years. MIPS, for instance, has only just merged.
- alex
--
Alex deVries
Vice President of Engineering
The Puffin Group
next prev parent reply other threads:[~1999-08-05 13:33 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
1999-08-05 13:48 ` Alex deVries [this message]
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=37A99641.EDD7A44@thepuffingroup.com \
--to=adevries@thepuffingroup.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 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.