Re: Overview of usage on each archive.

[Jason Helfman <jason.helfman@gmail.com>]

I agree with this, and beyond that, I think it would be a good idea to
print it out via csv, like the web page export, as an option. Maybe
good for reporting. Granted this is probably possible with a little
shell manipulation, but just thought I would throw it out there.

Thanks for the great backup software!
Jason

On Wed, Jan 6, 2010 at 11:08 AM, Gleb Arshinov <gleb@barsook.com> wrote:
> I'd separate option from command.  Can't immediately think of a Unix
> command which uses the same option and command.  Having one command do
> b, c, d is fine IMO.
>
> Best regards,
>
> Gleb
>
> Colin Percival wrote:
>>
>> Hi all,
>>
>> Morten Sjøgren wrote:
>>>
>>> 2010/1/6 James Seward <jamesoff@gmail.com <mailto:jamesoff@gmail.com>>
>>>    On Wed, Jan 6, 2010 at 5:36 PM, Morten Sjøgren <m_abs@mabs.dk
>>>    <mailto:m_abs@mabs.dk>> wrote:
>>>    > Essentially the data tarsnap prints right after a new archive is
>>>    created,
>>>    > just for existing archives.
>>>
>>>    Sort of like this?
>>>
>>> Yes, exactly like that. Thank you James. :)
>>
>> I'm starting to wonder if overloading "--print-stats" was a bad idea.  It
>> is
>> (a) an option which can be used in combination with -c or -d,
>> (b) a command which can be used on its own to print statistics for a
>> complete
>> archive set,
>> (c) a command which can be used with -f <archivename> to print statistics
>> for
>> an individual archive, and
>> (d) a command which can be used with -f '*' to print archive statistics
>> for
>> all archives.
>>
>> Would it be less confusing if I changed this?
>>
>



-- 
 "At any given moment, you may find the ticket to the circus that has
always been in your possession."