Date: Tue, 2 Jul 2019 13:05:40 +0200 From: Niclas Zeising <zeising@freebsd.org> To: Alexey Dokuchaev <danfe@freebsd.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r505641 - head/x11-toolkits/libXt Message-ID: <7085d1a0-c345-f879-6804-d3dde298ab17@freebsd.org> In-Reply-To: <20190702105011.GC59302@FreeBSD.org> References: <201907012119.x61LJVsX011853@repo.freebsd.org> <20190702102105.GA59302@FreeBSD.org> <358d47f5-cfa1-09df-a8bb-fbd75b7f8778@freebsd.org> <20190702105011.GC59302@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-07-02 12:50, Alexey Dokuchaev wrote: > On Tue, Jul 02, 2019 at 12:31:21PM +0200, Niclas Zeising wrote: >> On 2019-07-02 12:21, Alexey Dokuchaev wrote: >>> On Mon, Jul 01, 2019 at 09:19:31PM +0000, Niclas Zeising wrote: >>>> New Revision: 505641 >>>> URL: https://svnweb.freebsd.org/changeset/ports/505641 >>>> >>>> Log: >>>> x11-toolkits/libXt: Update to 1.2.0 >>>> >>>> Update x11-toolkits/libXt to 1.2.0 >>> >>> I couldn't help to notice that in many of your recent logs first two >>> sentences repeat each other, which is quite annoying to read (I trip >>> on the unexpected second occurrence of the same data, generate the >>> exception, and have to reread entire log again). Is there a reason >>> behind this, or it's some broken editor macro misbehaves? >> >> In general, the first line is a short summary, it shows up in for >> instance github as a summary of changes, and makes it possible to get >> an overview of many commits quickly. Afterwards, a more detailed >> explanation of the commit follows. > > Oh, so basically, if the log is in "one line header\n\n<body>" format, the > "real" log is <body>. Not sure if it's worth writing a procmail rule, but > I'll try to remember how to read these git-friendly(?) logs properly. Yes. I'm not sure if it's a git thing, or a github thing that other git utilities have mimicked. Looking at the git manual, it's mentioned there https://git-scm.com/docs/git-commit#_discussion (in case you want the background). I'll try to come up with something better in the cases the body part is mostly empty. Regards -- Niclas Zeising
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7085d1a0-c345-f879-6804-d3dde298ab17>