git: 6464fe05fe9d - main - - Update Unipro UGENE to version 38.1 and thus unbreak - CONFIG defaults to 64-bit mode now, adjust the check

Joseph Mingrone jrm at FreeBSD.org
Tue May 18 20:30:41 UTC 2021


On Tue, 2021-05-18 at 20:09, Alexey Dokuchaev <danfe at 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’s 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 987 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/dev-commits-ports-all/attachments/20210518/a301e5ad/attachment.sig>


More information about the dev-commits-ports-all mailing list