Date: Sun, 2 Apr 2017 00:03:35 +0200 From: Mathieu Arnold <mat@mat.cc> To: Cy Schubert <Cy.Schubert@komquats.com> Cc: Jason Unovitch <junovitch@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r416439 - head/sysutils/fusefs-ntfs Message-ID: <105cd6a7-80a1-7427-7173-ae95d053a856@mat.cc> In-Reply-To: <201704012157.v31LvDJq035490@slippy.cwsent.com> References: <201704012157.v31LvDJq035490@slippy.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Le 01/04/2017 =C3=A0 23:57, Cy Schubert a =C3=A9crit : > In message <02a45cdf-904b-1306-5d93-4dcc82f39cea@mat.cc>, Mathieu Arnol= d=20 > writes > : >> Le 01/04/2017 =C3=83 22:20, Cy Schubert a =C3=83=C2=A9crit : >>> There have been updates posted by the upline over the past 14 months = but no >> =20 >>> updates to the port. I'd like to update the port. >> Open a PR with the patch, and wait for the maintainer to either approv= e >> it or 14 days to timeout. > Already done. Lucky for me he approved very quickly. Having said that,=20 > personally, I expect a maintainer to keep a port up to date. That's now= I=20 > got my ports bit, initially. I kept submitting PRs and sending patches = to=20 > nectar@ (my ports mentor) until he literally got sick of my constant=20 > pestering and sent me an invite. I kind of think maintainers would want= to=20 > do that. It is what it is I guess. Yeah, which is why it is important to always open PR, so that, in case the maintainer is MIA you get a trace of the timeouts and you can reset the maintainership. --=20 Mathieu Arnold
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?105cd6a7-80a1-7427-7173-ae95d053a856>