Date: Wed, 10 Feb 2016 10:58:45 +0100 From: Kurt Jaeger <lists@opsec.eu> To: Peter Jeremy <peter@rulingia.com> Cc: Torsten Zuehlsdorff <mailinglists@toco-domains.de>, ports@freebsd.org Subject: Re: maintaining portmaster ? was: Re: Removing documentation Message-ID: <20160210095845.GD46096@home.opsec.eu> In-Reply-To: <20160210054726.GB35287@server.rulingia.com> References: <20160207000304.GA71035@eureka.lemis.com> <56B72E20.80909@toco-domains.de> <alpine.BSF.2.20.1602071700150.74300@wonkity.com> <56BA20DA.4080403@toco-domains.de> <20160209202456.GA46096@home.opsec.eu> <20160210054726.GB35287@server.rulingia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > >> I did take a look. I could do both: maintaining the port and maintaining > >> the software. What do you need? ;) > > > >Submit patches to the 12 PRs open for portmaster: > > > >https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=portmaster > > That is just being silly. Sorry if my mail was misinterpretable: I do not insist that Torsten has to fix every single PR to become maintainer, far from it. And I neither use portmaster nor synth in my setups, I use poudriere and portupgrade, so I'm not really part of the debate. Clearly, the documentation of the process in the handbook can be improved, and if this involves some words on alternatives, its even better. > Providing a patch for one of > the bugs would probably be sufficient for demonstrating interest > and ability. Yes, I understand that. It was not my intention to put up undue hurdles. -- pi@opsec.eu +49 171 3101372 4 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160210095845.GD46096>