From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 47A6F138334 for ; Thu, 27 Sep 2018 13:43:57 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3BCF3E0908; Thu, 27 Sep 2018 13:43:54 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id CF82BE0903 for ; Thu, 27 Sep 2018 13:43:53 +0000 (UTC) Received: from katipo2.lan (unknown [203.86.205.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: kentnl) by smtp.gentoo.org (Postfix) with ESMTPSA id D032E335C38 for ; Thu, 27 Sep 2018 13:43:50 +0000 (UTC) Date: Fri, 28 Sep 2018 01:43:23 +1200 From: Kent Fredric To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: What means bup? Message-ID: <20180928014323.2cd33680@katipo2.lan> In-Reply-To: References: <2118089b-4d6d-0a89-ce78-8d5597fb0141@gentoo.org> <20180718072657.fnz45gc44v3m4n6v@gentoo.org> <20180922203623.5ls6dcc73rifhuo5@gentoo.org> <20180924092757.5c714f9d@katipo2.lan> <20180923224527.y622ftpldrm7td2x@gentoo.org> <20180924142629.5483118a@katipo2.lan> Organization: Gentoo X-Mailer: Claws Mail 3.17.1 (GTK+ 2.24.32; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/JwwABtumL=QzuXjqkEA8atk"; protocol="application/pgp-signature" X-Archives-Salt: a915aac5-847c-4732-99b7-dff24c1e7585 X-Archives-Hash: 5914352c7f13dc13e00b69f7474d6c6d --Sig_/JwwABtumL=QzuXjqkEA8atk Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 24 Sep 2018 10:59:40 -0400 Alec Warner wrote: >=20 > So e.g.: >=20 > "Bump to x.y.z for bug 12345"? >=20 > Is there an annotation for "this commit is relevant to bug X, but does not > close bug X?" >=20 > I'm less sure we need the metadata all in the summary (because its suppos= ed > to be a summary.) > If the commits are annotated (Closes: bugX, BugRef: bugX...) we can amend > the tools to look at the annotatoins and not hand parse the summary. > It also helps for linkification. Well, yes, there's a limit to the summary length anyway that repoman enforces ;) But the point being to *maximise* the use of this "summary" message, and make good use of the "body" section of the "commit message". And there's already annotations for this in the body section, Bug: https://bugs.gentoo.org/123456 ( This references but does not close ) Closes: https://bugs.gentoo.org/123456 ( This closes ) In the summary line, you don't really need to clarify if it closes or not. Much of the benefit is knowing wilikins will see that message in #gentoo-commits, and then cite the entire bug summary in response. ( Including its current status of closed/open ) >=20 > > > > If I made changes in the ebuild in the bump itself, I'll attempt to > > describe the nature of those changes (from the perspective of the > > consumer)' > > =20 >=20 > You don't do that in the shortlog though..right? There is very little roo= m. See above. >=20 > Just for clarity, this all sounds like "changelog" stuff; are we still > generating changelogs from git commit descriptions? If so, this all seems > on the up and up to me. Generated changelogs are something that we were supposed to have, but they got culled from rsync tree for a host of reasons. ( One being they weren't generated in reverse-chronological order, which made them a boon to read ) But I still find having it documented useful even without this feature ( In the long term, we may find our users collectively start to prefer git to rsync, and having good change notes makes that even better for them ) --Sig_/JwwABtumL=QzuXjqkEA8atk Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEgdrME8Lrmai3DXYJda6SGagVg7UFAlus3ocACgkQda6SGagV g7XPVw//Y8ry2fCRa8lqkVDNNNjkCSGLfCny0oGxwk1hrtUiaQ3RdoqTZ9enP6Rg 567KZIaNE/pqjy62MkJzi5N36+2Ue8Hrh65jvAqW4rVsoWv5ULXxu8hVJhJdDpjt O2yBLuLQ0LV1FdJfAgYdkJOKxptLtrDxes7EswHx7m1F91t/M+65RlisiEtwFrZf KQBgxP0gBxCp1nrXQH8UgpkqpLkoH8e74kTbbYmsBamr8vwpE+XFZSDRNKpnkiXE 4UR/cxxWFyq2be8P66WcdZ71CHjVTgXSaJv4b8V6EGJduNBpGQ5QqKLE96oL8mo+ tidG+XwOgo22/b7gyKyJRbBMdRrD0o/XaQAJo6V26vwuWqbyHfV3kUzQxHt0WZZR JEU0RHjNSNCIwAqEBY/kKn6Mo4TSPbIpjgb2g3lOAlTUNv4505fO08hGX/m9WkwN tEbh7vae3i/OFRltyqJ3gNou/piWlqKW/5ErZfUoE2YOpOY+Sdi61dBtRwfMukOM gyIIN+h5wRAZU3PMb7f1lJmy+vGC0sI0gy/1S8crg0/VxIwO8V7cBv6UPfIlJg14 PuwkAbOR0p26DzJtSrCczKSddr6IPwiq/YaSKyFGq+HFm4J9KE5tGQWjzXId71ao 29TcivjO5EfMDrhhkPYpAjKhTPI7ucpkjGcQ0t2HWzgNmwCzKvk= =ta5D -----END PGP SIGNATURE----- --Sig_/JwwABtumL=QzuXjqkEA8atk--