Date: Thu, 15 Feb 2018 11:34:31 +0100 From: Kurt Jaeger <lists@opsec.eu> To: Walter Schwarzenfeld <w.schwarzenfeld@utanet.at> Cc: freebsd-ports@freebsd.org Subject: Re: New port: textproc/elasticsearch6 Message-ID: <20180215103431.GH89804@home.opsec.eu> In-Reply-To: <3c6e14f0-bd4c-ffc6-df78-1f6cd74eda05@utanet.at> References: <20180215090546.GB90204@blogreen.org> <3c6e14f0-bd4c-ffc6-df78-1f6cd74eda05@utanet.at>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > I don't think I makes sense to put it back to pool or tj@ is resetted > for elasticsearch ports. So someone other can take all elasticsearch > > port. As I wrote in my first answer: it is better one maintainer make > all elasticsearch ports. So please but tj@ for the moment back as > > maintainer. While adding a port with maintainer, then dropping that maintainer looks like it's according to the ports handbook, it at least violates the spirit. Giving the port to someone who's not very active right now, without him activily approving it was my mistake. I'll work on a solution (this evening CET). -- pi@opsec.eu +49 171 3101372 2 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180215103431.GH89804>