From: Andi Kleen <ak@suse.de>
To: Pavel Machek <pavel@suse.cz>
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [discuss] x86-64 2.4 tree in strict maintenance mode now
Date: Fri, 16 Apr 2004 17:46:34 +0200 [thread overview]
Message-ID: <20040416174634.601bee7c.ak@suse.de> (raw)
In-Reply-To: <20040416150027.GQ468@openzaurus.ucw.cz>
On Fri, 16 Apr 2004 17:00:27 +0200
Pavel Machek <pavel@suse.cz> wrote:
> Hi!
>
> > I will also not add workarounds for broken hardware to 2.4 anymore unless the change
> > is very simple and obvious (and even then it may be not worth it)
>
> This looks even more strict than Marcelo's rules... Is it wise?
Marcelo's rules should be the same now for 2.4.27 and later (modulo SATA)
In fact it has been this way for some time already (except for the IA32e merge,
which was a special case). This announcement just formalizes it.
-Andi
prev parent reply other threads:[~2004-04-16 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 15:43 x86-64 2.4 tree in strict maintenance mode now Andi Kleen
2004-04-16 15:00 ` [discuss] " Pavel Machek
2004-04-16 15:46 ` Andi Kleen [this message]
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=20040416174634.601bee7c.ak@suse.de \
--to=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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