From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: [PATCH 4/6] gnu: linux-libre-beagle-bone-black: Remove kernel variant. Date: Mon, 26 Sep 2016 13:31:09 -0400 Message-ID: <20160926173109.GB4625@jasmine> References: <20160926103447.31830-1-david@craven.ch> <20160926103447.31830-4-david@craven.ch> <20160926132344.GA23258@jocasta.intra> <20160926164934.GA25011@jocasta.intra> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48731) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1boZkR-0004s3-TG for guix-devel@gnu.org; Mon, 26 Sep 2016 13:31:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1boZkN-00048R-NZ for guix-devel@gnu.org; Mon, 26 Sep 2016 13:31:22 -0400 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:56174) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1boZkM-00046w-HE for guix-devel@gnu.org; Mon, 26 Sep 2016 13:31:19 -0400 Content-Disposition: inline In-Reply-To: <20160926164934.GA25011@jocasta.intra> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: John Darrington Cc: guix-devel --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 26, 2016 at 06:49:34PM +0200, John Darrington wrote: > Our current convention for commit messages is aesthetically pleasing, > but useless. It is redundant to put in the message WHAT has changed. > That can be easily determined by running "git show". What is much > more usefull is the reason WHY we changed it. I find the GNU changelog style to be very useful when reading the Git log.=20 There are certain types of commits that we make over and over again, especially with packages (updates, adding inputs, etc), and I find it helpful when their commit messages follow a common format. I agree that commits that don't conform to one of those types should have some explanation. This is why I often rewrite commit messages when I am committing on behalf of somebody else. But there is a value to "aesthetic" consistency. It's just like having standards for code style in my opinion. It helps a lot when reading others' commits. --envbJBWh7q8WU6mo Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJX6VtdAAoJECZG+jC6yn8IPCUQAOS13aYNFIQRtFH+jK8OQ0Rr OcPq+XehyOtrtB39k6AoIVFGYly95+eqCTKF9d5BBFu1mJWAoQmg6Y4eFj/eUm72 KBnCM/+9vvdjAymr+hFkX7zDPvTHT8GZd7r5QSPS89LmsQUG10yTKT+UU6uhiZrB seJ3rPdmYi6U0SHsunqV/6EzwoffhBNZSufzS8u6q0HBi3eBPV5/BvRXqyIQM7M/ 50M5RDAxamlibWT3QM3X2KtJvepe8eUmaDjnJxFVUo5iZbU301iQvDU/aYFbONid zvEotDoyvqXLrtemwrWqdgvsKpFW3Zr6I4k3JKRN9C3yadNYe4IQ+ZxFoRUY2o/K LpQCyhA8BZwG8jcWRVPt61b++xrES9uuJENwYUc3dmehckcMyfGlyK+YwMThUKGu p0OBfN5BOKfCOJwVr4a1MEI73WAo+DGJJMNgbhVEDiJySGTSWB1zQNxFkNqvx8mO eSre+WeDeTvf4WhaBOYNGJqcS2E2vhkbbGZTF/DOUNIVlMGHUOWp3g++b8L6sDia vNgpSprWcSI54wFC1kCMAhuQrj641wvTxbuuKJXsuuJrhFwSlyQO3VHf3ifU6Y0s 83fTQnALaQKDKXeY9rJgNhYxFhLqGe3pKYt5CsO1LWuE8YTNxhyaCh5u5WrXfORW 3ZvApWSd7MTtrKd7FTST =VD+/ -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo--