diff options
| author |  http://joeyh.name/ <http://joeyh.name/@web> | 2014-02-02 21:13:22 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2014-02-02 21:13:22 +0000 |
| commit | 1c1a5b0d451ded4f38a4dd9ce1c6761b0054ffce (patch) | |
| tree | 6c73e31d8a13f0291897e71fb9df9c27b4f4813c | |
| parent | c6a029d6e685689c99cf1786fc80e3d9ed1d3b42 (diff) | |
Added a comment
| -rw-r--r-- | doc/forum/git_annex_copy_more_informative_about_why_some_files_are_not_copied/comment_1_75445fc0e01ee99bae1c1f5a60e314bc._comment | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/forum/git_annex_copy_more_informative_about_why_some_files_are_not_copied/comment_1_75445fc0e01ee99bae1c1f5a60e314bc._comment b/doc/forum/git_annex_copy_more_informative_about_why_some_files_are_not_copied/comment_1_75445fc0e01ee99bae1c1f5a60e314bc._comment new file mode 100644 index 000000000..15373be70 --- /dev/null +++ b/doc/forum/git_annex_copy_more_informative_about_why_some_files_are_not_copied/comment_1_75445fc0e01ee99bae1c1f5a60e314bc._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="206.74.132.139" + subject="comment 1" + date="2014-02-02T21:13:21Z" + content=""" +I think that this behavior of git-annex is quite useful once you get used to it. It can sometimes trip up new users, but new users would not know about some --explain switch that made it say why it skipped each file. So, I consider this a documentation issue, and I've added a section to the walkthrough to help users learn about it: + +<http://git-annex.branchable.com/walkthrough/quiet_please:_When_git-annex_seems_to_skip_files/> + +As far as copy --from --to, it has been suggested before; I think there is even a todo about it somewhere, but such remote-to-remote transfers are expensive and I would hope it would not normally be used. +"""]] |