From fd5746caabb28998623c41af1d5228244484307c Mon Sep 17 00:00:00 2001 From: gernot Date: Wed, 12 Nov 2014 16:38:50 +0000 Subject: --- doc/bugs/Unclear_output_during_git-annex_copy.mdwn | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/bugs/Unclear_output_during_git-annex_copy.mdwn (limited to 'doc/bugs/Unclear_output_during_git-annex_copy.mdwn') 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 -- cgit v1.2.3