Date: Wed, 14 Apr 2021 11:58:22 +0200 From: Marc Fonvieille <blackend@freebsd.org> To: Mateusz Piotrowski <0mp@freebsd.org> Cc: Adriaan de Groot <adridg@freebsd.org>, ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org, Thomas Zander <riggs@freebsd.org> Subject: Re: Please use portname in first line of git commit message (git: 2a0f957e6215 - main - Update to upstream release 56.1.0.) Message-ID: <YHa8vj/dfuNJB9rU@emphyrio.blackend.org> In-Reply-To: <fc34a7f6-03f8-649c-4f26-2622da017c9e@FreeBSD.org> References: <202104130537.13D5b5ii008894@gitrepo.freebsd.org> <2434784.0dHE6SNnxz@beastie.bionicmutton.org> <fc34a7f6-03f8-649c-4f26-2622da017c9e@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Le 14.04.2021 11:48, Mateusz Piotrowski a écrit : > > The git email doesn't know what paths have been committed, and "just" uses the > > first line of the commit message. Many people now use > > > > <category>/<port>: <change summary> > > > > as the first line of the commit message, also because "git log" doesn't show > > files by default, and convenient git-history viewers like gitk and qgit show > > the first line of the commit message in overviews. Using this format for the > > first line of a commit message (followed by one blank line) helps all > > consumers of the git tree -- you can spot a couple by me that do *not* follow > > this format as well, that was before I realised that "this can be better". (It > > does take a while to develop the muscle memory to do it this way). > > > > [ade] > > Perhaps we could add a note about it to the commit message template for ports? > Yes, please. -- Marc
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YHa8vj/dfuNJB9rU>