Date: Tue, 18 May 2021 17:30:39 -0300 From: Joseph Mingrone <jrm@FreeBSD.org> To: Alexey Dokuchaev <danfe@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: <868s4b6az4.fsf@phe.ftfl.ca> In-Reply-To: <YKQfDRmDBp0NxB32@FreeBSD.org> (Alexey Dokuchaev's message of "Tue, 18 May 2021 20:09:49 %2B0000") References: <202105181525.14IFPYMT003113@gitrepo.freebsd.org> <86pmxo56wi.fsf@phe.ftfl.ca> <YKQfDRmDBp0NxB32@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On Tue, 2021-05-18 at 20:09, Alexey Dokuchaev <danfe@freebsd.org> wrote: > 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 The FreshBSD page seems to be showing full commit logs. I don't know how cgit implements their log display, but it's not a bug. It's a convention. See GIT-COMMIT(1). Though not required, it=E2=80=99s a good idea to begin the commit message with a single short (less than 50 character) line summarizing the change, followed by a blank line and then a more thorough description. The text up to the first blank line in a commit message is treated as the commit title, and that title is used throughout Git. For example, git-format-patch(1) turns a commit into email, and it uses the title on the Subject line and the rest of the commit in the body. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKkBAEBCgCOFiEEVbCTpybDiFVxIrrVNqQMg7DW754FAmCkI+9fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDU1 QjA5M0E3MjZDMzg4NTU3MTIyQkFENTM2QTQwQzgzQjBENkVGOUUQHGpybUBmcmVl YnNkLm9yZwAKCRA2pAyDsNbvnvcED/40m8o9vcGpNIrZs/xigmdTanwLGyyJcale /IwNetlcFxC16hQH5D0QSQqXuTenW90FOtO+NSXdX2k4K0QCZSVLyhHUymqZJu9C rsxdWAM938gcDYF3fCRLKlvi6IfnjczHHs4Pqmq0YSZP3k7AWziZjgbpooh6Ocpu 51a3RPu7Ro3TwTPRcm0a7IaDAje62CjgojkmcklKGOhgVY9HNqe+tWpGbubjf3An 4AmARxOrPg4KIPbRFMgrERqrEsS5uveTJY4FE4IdoG8fBM1FNWzl+3e/rvV6kMl6 4UBSqq+4nfl2mLoSZkl9vi8+laYnJxB5C1jPQO8uqQulS6M9MMz2qtEavn8uJQDw KsxjTxEJTEdsAFVEX6j4eL2j28B3P606XCVjuMJaJQKrJ3cmIQy9uYnyBZYPMIq7 tJccb1jd93Ew4DkmEGijvsHhfTXj4jVEsfQA83CViRFXRKwp/1QMiUu3dsURthit Tp8C9sWwunXXZ1wis8ijD2oY3b7ChyWxaACXjP7TExzYvz4c3FVx+NmrxY+iMS0p v78QCxHB96bI8h5IA++WNu37GRmX0m0SY+5RS9yIYE+OF1/28qaoeen7bvv1LIlq Bu/g8y1o0XGPIKF79Strg7Co+Sle4nIp/T9FayK338IfLmgcGvu5V9UBBPSslK6E 8324zHXh5g== =Tjpa -----END PGP SIGNATURE----- --=-=-=--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?868s4b6az4.fsf>