Zbigniew Jędrzejewski-Szmek wrote: > tl;dr: you want to fix changelog entries. That's supported by saving the > generated changelog to 'changelog' file and doing whatever edits you want > there. > > With that approach, you can do arbitrary formatting and fixups. The > advantage compared to status quo (non-autochangelog) is that you only need > to do it if the autogenerated changelog is deficient for whatever reasons. > In the default case you can use autochangelog, and fall back to the manual > version when necessary. [snip] > Rpmautospec allows you to have a part or parts of a commit message that > end up in the changelog, and parts that do not, see > https://docs.pagure.org/fedora-infra.rpmautospec/autochangelog.html#changelog-entries-generated-from-commit-messages All in all a very complicated and error-prone process just to save some extremely lazy packagers a 5-second copy&paste. I really do not see why that should be the default and recommended process. The rules how to format the commit message are error-prone, and if you get them wrong, you usually only notice when it is too late to fix it (because force-pushes are not allowed). Yes, you can manually run "rpmautospec generate-changelog", but that is actually no less effort than just taking care of the changelog manually to begin with. Kevin Kofler _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
