diff options
author | 2014-11-12 15:53:06 -0400 | |
---|---|---|
committer | 2014-11-12 15:53:06 -0400 | |
commit | 94f4698441e58316494d46af0d2c9f8374bf89ff (patch) | |
tree | 4eb0b79cf17054687421ebbc6670ab638263a56d /doc | |
parent | bb7571aeb4d4cd4920a7fe4b2538ce5a412f7603 (diff) | |
parent | fd5746caabb28998623c41af1d5228244484307c (diff) |
Merge branch 'master' of ssh://git-annex.branchable.com
Diffstat (limited to 'doc')
-rw-r--r-- | doc/bugs/Unclear_output_during_git-annex_copy.mdwn | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/bugs/Unclear_output_during_git-annex_copy.mdwn b/doc/bugs/Unclear_output_during_git-annex_copy.mdwn new file mode 100644 index 000000000..72485d1a6 --- /dev/null +++ b/doc/bugs/Unclear_output_during_git-annex_copy.mdwn @@ -0,0 +1,15 @@ +I noticed the following output during a `git-annex sync --content` run +which I found a little disconcerting: + + copy file.idx copy file.idx (gpg) (checking s3...) (to s3...) + ok + copy file.pack copy file.pack (checking s3...) (to s3...) + ok + (Recording state in git...) + +It's confusing that seemingly only the first file got encrypted (gpg). + +Fortunately, it appears that actually all files were encrypted (only GPGHMAC file names in remote location), +so this is hopefully just a cosmetic issue. + +git-annex version: 5.20141024-g613f396 |