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 849E1138334 for ; Mon, 24 Sep 2018 02:27:48 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 534D5E08C2; Mon, 24 Sep 2018 02:27:44 +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 DD2FEE077C for ; Mon, 24 Sep 2018 02:27:43 +0000 (UTC) Received: from gentoo.org (unknown [IPv6:2001:470:e1cc:3::10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: prometheanfire) by smtp.gentoo.org (Postfix) with ESMTPSA id 7134F335D2C for ; Mon, 24 Sep 2018 02:27:42 +0000 (UTC) Date: Sun, 23 Sep 2018 21:27:39 -0500 From: Matthew Thode To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: What means bup? Message-ID: <20180924022739.qqfq2z4omkqwtnww@gentoo.org> References: <2118089b-4d6d-0a89-ce78-8d5597fb0141@gentoo.org> <20180718072657.fnz45gc44v3m4n6v@gentoo.org> <20180922203623.5ls6dcc73rifhuo5@gentoo.org> <20180924092757.5c714f9d@katipo2.lan> 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-sha512; protocol="application/pgp-signature"; boundary="bmnzyjgk65fpxjez" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716 X-Archives-Salt: 186f3789-940f-4acd-8008-bd708bd72ab5 X-Archives-Hash: 63ea874cfc86ea1a50394fb582aa1e24 --bmnzyjgk65fpxjez Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 18-09-23 21:39:01, Alec Warner wrote: > On Sun, Sep 23, 2018 at 6:53 PM M. J. Everitt wrote: >=20 > > On 23/09/18 22:27, Kent Fredric wrote: > > > On Sat, 22 Sep 2018 15:36:23 -0500 > > > Matthew Thode wrote: > > >> My hand slipped. What ever happened to assuming the best :( Are you > > >> going to ping the list every time my hand slips up and I mistype > > >> something? Not sure you'll have time for it :P > > > Personally, I would love it if more people tried harder to provide > > > meaningful commit messages. > > > > > > "bup" vs "bump" isn't really achieving much, just one of the two are > > > substantially more egregious. > > > > > > Perhaps, if the commit messages were crafted with clarity as their > > > intent, the consequence of accidental typos would be much more > > > inconsequential. > > > > > > ( I seriously think we could do with a *little* more chiding here than > > > we generally see, but like, I'm typically just biting my tongue every > > > time somebody doesn't invest any more effort than to write the word > > > "bump" in their text editor when committing with repoman, cos I really > > > don't want to be a dick about it. There's room for more than 4 > > > characters and a space in the subject, and infinitely more space in t= he > > > body, why do we have to choose the least clear of all options? ) > > > > > > Occasional accidents are still gonna happen, but it would be nice if = we > > > didn't define accidents and siblings of accidents as the status quo. > > > > > I think Kent has pretty much the point here .. we try to stipulate that > > the commit message describes what the update is, and is clear for *all* > > users of the repository, and not just the relevant maintainer. There is > > also a cronic double-standard for existing or long-standing devs, and > > newer devs, recruits and proxy-maintainers (who get a double-scrutiny > > typically) - and I could easily see how this breeds resentment... > > > > Perhaps it would be simple enough to add a check to repoman for commit > > messages less than 10 characters, and with at least one *additional* > > space, mandating two words in the commit message. It seems draconian, > > but if developers continue to be lazy, what choice does one have?! > > > > > I don't see a problem with 'version bump' as a description. Sometimes you > bump an ebuild because upstream released a new version and you want to > track. I'm fairly against changes describing what was changed (typically > the reader can git show and observe the changes.) The useful information = is > *why* the change was made. Sometimes its because "upstream released a new > version." >=20 > Like Matt I'm curious what others expect to see in the description. >=20 That's exactly why I release much of the stuff I do, I get a task in todoist via ifttt monitoring a github atom feed that a new release is out and I package it. --=20 Matthew Thode (prometheanfire) --bmnzyjgk65fpxjez Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEExFR3cOKGRpGbcMHPZKN76q4ZpOgFAluoS5oACgkQZKN76q4Z pOib5Q//Ren6+Gt1bz6993O388zZDKvQVR+J9l8C5bVDsFN7s2RrmJwSCy2avON8 tudmkj22/VEEwqwYWqKO5bY3/wKJSJM3FXRQIRaGDgMOV8U9Km1b9ps0BBCEjVQt wkNwfHi0HVUYO9MD3cb1WIpBadob3A8v/3G0xmyV+Kid9mhwILp4rOX+fO3Pesdy o+jjFqUD1f9qvSGMszzO+c0JrJIckc2hfzFsbgVBMWKBDHa371wb2zyLO8K1N4Zl iE5pccTVDYFQi1nBXPIlkZjL+tWu7fcIoQFbcTAPBdyg45AXn481mFmnbyQ4umlk rUz2aBJO/zqFX+jHOl0DTz+Aga5YBhp4va3hfqg4ZPYBH3RpoUpak9d7BBFWuqzv hWpMY0TjJsUfm8SQpiBAOhK+ItTKmpITugbxxE9oBQf1viStQWZaSBX9grr2NmOW yKaqexd8SmoqBmAXVTZhScgJq7+89Gk/v9drbzhXlnoxxNYqwXP/aSvRvAQ4Fxpq BCd2PdU6HjqW6eU4Vx8XKLkDv8YEaCrN72ST4wCr3sNm+r1cIAUtZh904wqmjXvG woExhtykkuIaqD205Hd8HHNGFoQuADTz9SKuVb3O1OSVbAj9yWbxLOY5IrAEShS5 TG2QbsSpHFtgvmO3hYagawnaUGbJ3q+SoY8W1qTvExl4gAt+4tM= =PeSW -----END PGP SIGNATURE----- --bmnzyjgk65fpxjez--