From: Pavel Machek <pavel@suse.cz>
To: Andi Kleen <ak@suse.de>
Cc: discuss@x86-64.org, announce@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:00:27 +0200 [thread overview]
Message-ID: <20040416150027.GQ468@openzaurus.ucw.cz> (raw)
In-Reply-To: <20040414174353.1dcbda16.ak@suse.de>
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?
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
next prev parent reply other threads:[~2004-04-16 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 15:43 Andi Kleen
2004-04-16 15:00 ` Pavel Machek [this message]
2004-04-16 15:46 ` [discuss] " Andi Kleen
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=20040416150027.GQ468@openzaurus.ucw.cz \
--to=pavel@suse.cz \
--cc=ak@suse.de \
--cc=announce@x86-64.org \
--cc=discuss@x86-64.org \
--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
all inboxes | Powered by JetHome®