Date: Tue, 18 May 2021 20:09:49 +0000 From: Alexey Dokuchaev <danfe@freebsd.org> To: Joseph Mingrone <jrm@freebsd.org> Cc: ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: git: 6464fe05fe9d - main - - Update Unipro UGENE to version 38.1 and thus unbreak - CONFIG defaults to 64-bit mode now, adjust the check Message-ID: <YKQfDRmDBp0NxB32@FreeBSD.org> In-Reply-To: <86pmxo56wi.fsf@phe.ftfl.ca> References: <202105181525.14IFPYMT003113@gitrepo.freebsd.org> <86pmxo56wi.fsf@phe.ftfl.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 18, 2021 at 01:43:57PM -0300, Joseph Mingrone wrote: > ... > Here are some snippets of what can be seen with git log --oneline. It's a known bug in Git, for some reason it does not stop at first \n. Interestingly, cgit web frontend does not exhibit this problem, does it use some smarter form of shortlog? The main point, however, is that commit logs should not contain what can be easily and automatically inferred from the commit itself. As an example of sanity, have a look at https://freshbsd.org/freebsd, which infers correct commit headers and clearly shows how needlessly noisy those "canonical" logs start to look like if you do things the right way. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YKQfDRmDBp0NxB32>