From: Marc Espie <espie@quatramaran.ens.fr>
To: mrs@windriver.com
Cc: gcc@gcc.gnu.org
Subject: Re: MAINTAINERS policy question
Date: Tue, 18 Sep 2001 16:30:00 -0000 [thread overview]
Message-ID: <200109182326.f8INQiM16772@quatramaran.ens.fr> (raw)
In-Reply-To: <200109180038.RAA27823@kankakee.wrs.com>
In article < 200109180038.RAA27823@kankakee.wrs.com > you write:
>would be OK by the sony_news/mips maintainer. My wording also makes
>it clear that an FreeBSD maintainer can change the FreeBSD make file
>fragments, but not the Linux parts of the x86 files. Adding a
I'm looking at the 3.0.1 MAINTAINER list. There is no FreeBSD maintainer,
nor a Linux maintainer, nor an OpenBSD maintainer.
In fact, considering the current discussion, what's the interpretation of
`port' ? I don't think it's unnatural to consider it might mean `processor'
(current interpretation) but may also mean `os' or `processor+os'.
The area is fairly simple to define.
If I don't presume too much, I would like to be relisted a maintainer for
the OpenBSD ports (the OpenBSD specific part, of course, by your rules).
next prev parent reply other threads:[~2001-09-18 16:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-17 17:40 mike stump
2001-09-18 16:30 ` Marc Espie [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-17 9:44 Ulrich Weigand
2001-09-16 11:46 Richard Kenner
2001-09-16 12:24 ` Andreas Jaeger
2001-09-16 8:38 Richard Kenner
2001-09-16 6:39 Richard Kenner
2001-09-16 8:35 ` Daniel Berlin
2001-09-16 6:04 Ulrich Weigand
2001-09-16 18:19 ` DJ Delorie
2001-09-16 2:52 Bernd Schmidt
2001-09-16 3:12 ` Andreas Jaeger
2001-09-16 3:38 ` Graham Stott
2001-09-16 10:59 ` Mark Mitchell
2001-09-16 11:16 ` Andreas Jaeger
2001-09-16 11:17 ` Mark Mitchell
2001-09-16 11:22 ` Toon Moene
2001-09-16 11:23 ` Gerald Pfeifer
2001-09-16 14:14 ` David Edelsohn
2001-09-17 8:32 ` Phil Edwards
2001-09-16 4:06 ` Joseph S. Myers
2001-09-16 15:04 ` Joe Buck
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=200109182326.f8INQiM16772@quatramaran.ens.fr \
--to=espie@quatramaran.ens.fr \
--cc=gcc@gcc.gnu.org \
--cc=mrs@windriver.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).