Date: Thu, 3 Jun 2021 00:30:10 +0200 From: Michael Gmelin <grembo@freebsd.org> To: Gerald Pfeifer <gerald@pfeifer.com> Cc: Mathieu Arnold <mat@freebsd.org>, ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: Replacing USE_GCC=any and the danfe@ filter (was: svn commit: r568012 - head/net/tightvnc) Message-ID: <DEA7DC86-8627-4E28-B53A-055BFF4B7F7D@freebsd.org> In-Reply-To: <f7316636-5fd2-cfd1-7661-3044fd782587@pfeifer.com>
index | next in thread | previous in thread | raw e-mail
> On 3. Jun 2021, at 00:23, Gerald Pfeifer <gerald@pfeifer.com> wrote: > > On Sun, 30 May 2021, Mathieu Arnold wrote: >> Thank you for working on this. > > So, I was just ready to commit the next step and prepared a nice git > style commit message: > > Replace USE_GCC=any with USE_GCC=yes > > USE_GCC=any has been equivalent to USE_GCC=yes in most cases (such > as i386 and amd64 since 12.x and depending on configuration 11.x, > most newer installations on other platforms, and 13.x across the > board). > > Since commit 96c17633d90386b5bcf8 Mk/bsd.gcc.mk ... > > Alas, the danfe@ filter struck: > > remote: Resolving deltas: 100% (111/111), completed with 111 local objects. > remote: > remote: ================================================================ > remote: First line does not start with the regular > remote: category/port: subject > remote: ================================================================ > > What now? My commit message generator[0] would suggest: "category1/port1, category2/port2, and N more: your text here" I don’t know if this is still possible with the remote commit hook though. [0] https://github.com/grembo/committer-tools/blob/main/ports-prepare-commit-msg > > Neither "*/*: Replace USE_GCC=any..." in the subject nor a couple dozen > individual commits strike me as desirable. > > Geraldhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DEA7DC86-8627-4E28-B53A-055BFF4B7F7D>