Date: Thu, 3 Jun 2021 15:09:45 +0200 From: Matthias Andree <matthias.andree@tu-dortmund.de> To: Torsten Zuehlsdorff <freebsd@toco-domains.de>, Mathieu Arnold <mat@freebsd.org> Cc: ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: Rule/Change-Update-Newsletter? (was: Re: Replacing USE_GCC=any and the danfe@ filter (was: svn commit: r568012 - head/net/tightvnc)) Message-ID: <354822a0-a1d4-a4c6-2dbb-de05828ceade@tu-dortmund.de> In-Reply-To: <6642da17-a2da-d3d0-444f-d761f2a56840@toco-domains.de> References: <f7316636-5fd2-cfd1-7661-3044fd782587@pfeifer.com> <20210603063235.676vy42y56fzvuu5@aching.in.mat.cc> <64998e65-5200-ba36-eb61-f54b26a6e2a8@toco-domains.de> <0506d5b7-3a2e-89eb-8e72-238b7a3f3d4d@toco-domains.de> <20210603101652.v2nk3kuvbayokd2g@aching.in.mat.cc> <6642da17-a2da-d3d0-444f-d761f2a56840@toco-domains.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 03.06.21 um 12:40 schrieb Torsten Zuehlsdorff: > Without any judgment of this rule (here): i really have no idea that: > 1) We have such a new hook > 2) We changed the New port rule > > That raises to issues directly: > 1) I am annoyed that this was not discussed (maybe in a way i noticed?) > 2) I am annoyed that this change was not made clear to the committer > involved. > > To address point 2: can we at least aim for a Newsletter (or a mail to > ports-committer@) when we do such think. I really do NOT scan the > porter-handbook for changes on a regular base (while i could also NOT > find the change there). It would be very nice if we can be up to date to > all relevant changes without reading through dozens of mailinglists or > thousands of commit messages. Or has the E_NOTIME reason of most > developer changed to E_HAVETIME? It it really a terrible idea to inform > the team? Such information would belong into ports/CHANGES, but we've had many changes that are not documented there.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?354822a0-a1d4-a4c6-2dbb-de05828ceade>