[git-buildpackage] gbp-dch commit message order

[Guido Günther]

Hi,
On Tue, Dec 28, 2021 at 01:26:14PM +0100, Stephan Skrodzki wrote:
> As I am not really working with tags, I rebuild the changelog for every new
> package release from scratch. The version I set is
> major-minor-YYYYMMDDHHMMSS e.g. 0.2-20211228124024
> 
> Now as I see, the git log messages are added to the changelog in time order,
> so at the and, the oldest message is on the top.
> 
> If I understand right, this could be avoided by setting tags for each new
> version and then only update the changelog. But even inside the updates, I'd
> say, that the reverse updated order would be more useful?

Debian policy does not mandate anything here so both orders are fine. A
patch (with tests) making this configurable wouldn't hurt at all.
Cheers,
 -- Guido

> 
> To get the behaviour intended (at least for me) I have commented out
> commits.reverse() in the dch.py script. Would it make sense to have this at
> least optional with a switch?
> 
> Cheers
>  Steve
> 
> _______________________________________________
> git-buildpackage mailing list
> git-buildpackage at lists.sigxcpu.org
> http://lists.sigxcpu.org/mailman/listinfo/git-buildpackage