Date: Tue, 18 Jan 2000 22:54:21 +0200 From: Mark Murray <mark@grondar.za> To: Brian Fundakowski Feldman <green@FreeBSD.org> Cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, 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: <200001182054.e0IKsLw00815@gratis.grondar.za> In-Reply-To: <Pine.BSF.4.10.10001181508050.36128-100000@green.dyndns.org> ; from Brian Fundakowski Feldman <green@FreeBSD.org> "Tue, 18 Jan 2000 15:11:33 EST." References: <Pine.BSF.4.10.10001181508050.36128-100000@green.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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.
What is MAINTAINER[S] used for? That needs to be addressed, not
Makefile syntax.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.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?200001182054.e0IKsLw00815>