From: Ralf Baechle <ralf@linux-mips.org>
To: linux-mips@linux-mips.org
Subject: Linux 2.4 future
Date: Mon, 1 Dec 2003 23:46:24 +0100 [thread overview]
Message-ID: <20031201224624.GA13412@linux-mips.org> (raw)
For those of you who don't follow linux-kernel below Marcelo's posting
about the future of 2.4. I think we should follow that for MIPS also,
so whatever new feature you still may have pending for 2.4, send it
soon - or for 2.6.
I also remind everybody that a 2.6.0 release is expect already before the
end of the year and the MIPS kernel is not exactly in the shape we'd
like it to be - time to switch to 2.6 for active development!
Ralf
----- Forwarded message from Marcelo Tosatti <marcelo.tosatti@cyclades.com> -----
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Date: Mon, 1 Dec 2003 12:25:23 -0200 (BRST)
To: linux-kernel@vger.kernel.org
Subject: Linux 2.4 future
Content-Type: TEXT/PLAIN; charset=US-ASCII
Hi,
The intention of this email is to clarify my position on 2.4.x future.
2.6 is becoming more stable each day, and we will hopefully see a 2.6.0
release during this month or January.
Having that mentioned, I pretend to:
- Fix pending problems which might required more intrusive modifications
during 2.4.24. New drivers will be accept during this period (for example,
Cyclades PC300 driver, input userlevel driver support, or other sane
driver which might come up).
- From 2.4.25 on, fix only critical/security problems.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
----- End forwarded message -----
Ralf
reply other threads:[~2003-12-01 22:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20031201224624.GA13412@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.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