[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] Usability annoyance
From: |
edgar . soldin |
Subject: |
Re: [Duplicity-talk] Usability annoyance |
Date: |
Sat, 31 Dec 2011 14:10:34 +0100 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 |
On 30.12.2011 02:26, Ken Bass wrote:
> Maybe I am doing something incorrect, but when listing collections (such as
> collection-status), duplicity prints out something like:
>
> Chain start time: Thu Dec 29 19:08:30 2011
> Chain end time: Thu Dec 29 19:08:30 2011
> Number of contained backup sets: 1
> Total number of contained volumes: 1
> Type of backup set: Time: Num volumes:
> Full Thu Dec 29 19:08:30 2011
> 1
this is because this output is optimized for user readability
> However, when restoring (using the -t, --restore-time, --time) you cannot
> cut/paste that date. Instead you need to perform conversion on the date.
> I would like to suggest/propose that the listings be changed so that they
> print the 'w3' date.
>
> I could either be changed outright to print
> Full 20111230T000830Z 1
you can use --log-fd to retrieve machine readable output in that format
>
> Or perhaps added to existing output such as
>
> Chain start time: Thu Dec 29 19:08:30 2011
> Chain end time: Thu Dec 29 19:08:30 2011
> Number of contained backup sets: 1
> Total number of contained volumes: 1
> Type of backup set: Time:
> Num volumes:
> Full Thu Dec 29 19:08:30 2011 (20111230T000830Z)
> 1
>
do you do more than one backup per day? because if not you might easily use
2011-12-30 as time value. check
http://duplicity.nongnu.org/duplicity.1.html#sect8
i don't really oppose to your patch but i am not sure it is desperately needed.
..ede/duply.net