diff options
| author |  liori@cfce7a5e6e71574f82591d8cfe689cf3ac8516a4 <liori@web> | 2016-07-03 19:43:46 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2016-07-03 19:43:46 +0000 |
| commit | f2948d98fe7ca6c2a160828975729f898a1637a1 (patch) | |
| tree | a10685fbe2c621380e06ed08ff1c28d3eca22b27 | |
| parent | 1caf3a2829098c8dbcf9c06b048e56f62e9162dd (diff) | |
| -rw-r--r-- | doc/forum/__96__git_annex_copy__96____44___estimate_how_much_data_to_copy.mdwn | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/forum/__96__git_annex_copy__96____44___estimate_how_much_data_to_copy.mdwn b/doc/forum/__96__git_annex_copy__96____44___estimate_how_much_data_to_copy.mdwn new file mode 100644 index 000000000..dcc3377ed --- /dev/null +++ b/doc/forum/__96__git_annex_copy__96____44___estimate_how_much_data_to_copy.mdwn @@ -0,0 +1,3 @@ +Hi, + +Is there any way to estimate how much data will be transferred and/or written down on the target repository of a `git annex copy` command? Something that would take into account that some data is already there, etc. |