[Duplicity-talk] [patch] collection-status: output in more consistent order

[Peter Schuller]

Everytime I use collection-status my brain has a hiccup as a result of
the most recent backup being listed first, with older backups listed
later in internally latest-last order. And in both cases sets within a
chain are listed in latest-last order.

Since the normal case is that you have zero or more backup chains
without matching signatures, and then one (latest) backup chain with
matching signatures, I feel it is much more natural to print the ones
without matching signatures first. This should result in a more
natural chronological order in most typical cases.

Attached patch simply changes the order of the collection status.

-- 
/ Peter Schuller

PGP userID: 0xE9758B7D or 'Peter Schuller <address@hidden>'
Key retrieval: Send an E-Mail to address@hidden
E-Mail: address@hidden Web: http://www.scode.org

duplicity-colstatsreverse.patch
Description: Text Data

pgpR_42S1Ddsq.pgp
Description: PGP signature