Ühel kenal päeval, P, 23.09.2018 kell 21:39, kirjutas Alec Warner: > 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." > > Like Matt I'm curious what others expect to see in the description.
I expect to see the version number being bumped to. At least something like "cat/pkg: bump to 1.2.3" This help tremendously for git shortlog, and just "bump" is something you do all the time, so not a good summary. But bump to a specific version is a good summary, as it says it exactly enough and in summary. However Matthew does that already, in the form of "cat/pkg: 1.2.3 bump". I don't agree with "bup", but it indeed mostly has been "bump" now, and my only problem there is that I'm not used to that order (vs "bump to 1.2.3"). Mart
signature.asc
Description: This is a digitally signed message part
