From: "David S. Miller" <davem@redhat.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-arch@vger.kernel.org
Subject: Re: Future of linux-arch
Date: Sun, 28 Mar 2004 12:55:03 -0800 [thread overview]
Message-ID: <20040328125503.7142af94.davem@redhat.com> (raw)
In-Reply-To: <20040328214819.F10358@flint.arm.linux.org.uk>
On Sun, 28 Mar 2004 21:48:19 +0100
Russell King <rmk@arm.linux.org.uk> wrote:
> Well, I'm sick to death with this issue. Someone else can sort out
> this problem.
The reality is that akpm asked me to create this alias so that
two things could happen:
1) Andrew could contact all arch maintainers when he was messing with
something that could break platforms or needed explicit platform support.
2) Arch maintainers could notify each other of problems they've found
in their own arch code which applies to other platforms as well.
So far it's worked wonderfully at both of these things.
You're worked up over a seperate issue and the fact that hch is being
his usual fucknut self about things like this, just ignore him and do
the fantastic job you always do Russell.
prev parent reply other threads:[~2004-03-28 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-28 11:01 Future of linux-arch Russell King
2004-03-28 20:29 ` David S. Miller
2004-03-28 20:48 ` Russell King
2004-03-28 20:55 ` David S. Miller [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=20040328125503.7142af94.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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