Date: Tue, 18 Jan 2000 15:11:33 -0500 (EST) From: Brian Fundakowski Feldman <green@FreeBSD.org> To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com> Cc: Munechika SUMIKAWA <sumikawa@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: ports/security/openssh Makefile ports/security/openssh/patches patch-ad Message-ID: <Pine.BSF.4.10.10001181508050.36128-100000@green.dyndns.org> In-Reply-To: <99185.948223720@zippy.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 18 Jan 2000, Jordan K. Hubbard wrote:
> > Mea culpa. I didn't mean to hurt anything by adding sumikawa as
> > another MAINTAINER like that :) Munechika, what do you think about
> > adding yourself as MAINTAINER2= sumikawa? That wouldn't break
>
> Before you make suggestions about how to solve this, let's discuss the
> "multiple maintainer problem" in more detail. We don't need a kludge
> to this one, we need a real mechanism which allows for this so we don't
> end up back in this discussion again.
>
Well, ideally, this is how I would do it:
MAINTAINER= green@FreeBSD.org # Backward compatibility
# And then a comma/space-delimited new one:
MAINTAINERS= green@FreeBSD.org, sumikawa@FreeBSD.org
That would only possibly break bad scripting (but not correct scripting),
and it would provide a mechanism for more MAINTAINERS. My ideal choice
for separator tokens would be ", ^I". Wouldn't this be a clean and
compatible solution? Nothing special about the ${MAINTAINERS} variable
would even have to be implemented until it's convenient.
> - Jordan
--
Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! /
green@FreeBSD.org `------------------------------'
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.10001181508050.36128-100000>