One of my USB drives just died, so I'm doing a 'git annex get --not
--copies 1' to re-attain data redundancy. It seems that a new rsync
instance is invoked for each file? In my case, I have thousands of
photos which are big enough to be worth annexing but still not
individually huge, so it seems
Adam Spiers wrote:
> One of my USB drives just died, so I'm doing a 'git annex get --not
> --copies 1' to re-attain data redundancy. It seems that a new rsync
> instance is invoked for each file? In my case, I have thousands of
> photos which are big enough to be worth annexing but still not
> in
On Wed, Jan 18, 2012 at 4:09 PM, Joey Hess wrote:
> Adam Spiers wrote:
>> One of my USB drives just died, so I'm doing a 'git annex get --not
>> --copies 1' to re-attain data redundancy. It seems that a new rsync
>> instance is invoked for each file? In my case, I have thousands of
>> photos whi
Hi,
about _filter_and_handle_action()
https://gitorious.org/dvcs-autosync/dvcs-autosync/blobs/master/dvcs-autosync#line406
well actually the most important stuff is my point 3, you might want to read
that first. It could make all else moot.
1) line 431: why the break? why stop processing?
what
Adam Spiers wrote:
> OK. You mean this?
>
> http://git-annex.branchable.com/todo/parallel_possibilities/
More like this:
http://git-annex.branchable.com/todo/wishlist:_Prevent_repeated_password_prompts_for_one_command
> > You can enable ssh's connection sharing though. (ControlMaster)
>
>