%changelog not in descending chronological order

[Jacek Konieczny]

On Mon, Jul 16, 2012 at 03:47:41PM -0400, Jeffrey Johnson wrote:
> b) will introduce some incompatibilities: for starters,
> there's functionality already implemented to truncate
> change log's by number/oldest that will break if you
> just go unordered.

But that would be not 'totally unordered'. GIT history is just not
linear, so there is no 'one real chronological order'. What is currently
generated is enough for such features like 'truncate to last X entries',
it is just not 'chronological enough' for RPM.

RPM doing the sorting may in fact break the history – RPM does not know
full history from the short git log excerpts. E.g. an old commit (made long
time ago on a development branch) just recently added to the master
branch could be moved past the truncation point. 

I also think that patching RPM may be the best choice here – easy and
effective.

Greets,
        Jacek