From: Karim Yaghmour <karim@opersys.com>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Zwane Mwaikambo <zwane@arm.linux.org.uk>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Updating real-time and nanokernel maintainers
Date: Thu, 18 Dec 2003 19:11:55 -0500 [thread overview]
Message-ID: <3FE2424B.70901@opersys.com> (raw)
In-Reply-To: <3FE23E3F.2000801@cyberone.com.au>
Nick Piggin wrote:
> I agree with Zwane. People have enough trouble using MAINTAINERS
> as it is. Using it to pat each others backs makes it less useful.
I understand what you mean.
> As Zwane said, neither have code in the kernel, so I don't see how
> you think it is justified...?
It is justified in the same way that the RTLinux entry was justified
for those many years. But the bottom line is as I said it before,
I personally have no take in this, and I certainly don't want to
start a debate on the use of the MAINTAINERS file, others are much
more apt than myself to make the proper judgement call on the proper
use of that file.
Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 514-812-4145
next prev parent reply other threads:[~2003-12-19 0:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 23:14 [PATCH] Updating real-time and nanokernel maintainers Karim Yaghmour
2003-12-18 23:22 ` Zwane Mwaikambo
2003-12-18 23:33 ` Karim Yaghmour
2003-12-18 23:40 ` Zwane Mwaikambo
2003-12-18 23:48 ` Karim Yaghmour
2003-12-18 23:54 ` Nick Piggin
2003-12-19 0:11 ` Karim Yaghmour [this message]
2003-12-19 9:41 ` Jörn Engel
2003-12-21 8:27 ` [PATCH] Updating real-time and nanokernel maintainersy yodaiken
2003-12-21 19:22 ` Karim Yaghmour
2003-12-21 19:56 ` Linus Torvalds
2003-12-21 22:51 ` Jamie Lokier
2003-12-22 2:58 ` Karim Yaghmour
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=3FE2424B.70901@opersys.com \
--to=karim@opersys.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
--cc=torvalds@osdl.org \
--cc=zwane@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