diff options
| -rw-r--r-- | doc/bugs/--quite_with_s3.mdwn | 23 | ||||
| -rw-r--r-- | doc/bugs/Automatic_upgrades_should_be_cryptographically_signed/comment_1_37ed871c82879a31c2d8cfc7d9736548._comment | 10 |
2 files changed, 33 insertions, 0 deletions
diff --git a/doc/bugs/--quite_with_s3.mdwn b/doc/bugs/--quite_with_s3.mdwn new file mode 100644 index 000000000..f087b2bc6 --- /dev/null +++ b/doc/bugs/--quite_with_s3.mdwn @@ -0,0 +1,23 @@ +### Please describe the problem. + +When copying files to s3 using, + + git annex copy --quiet --to mys3 --fast + +No information whatsoever is printed during upload when ran without `--quite` it prints a line for each file in the repo creating page after page of output for repos with thousands of file basically no way to tell which files got uploaded. Is it possible to have a verbosity level between quite and verbose that only reports progress on actual copy/move operations. + +### What steps will reproduce the problem? + + +### What version of git-annex are you using? On what operating system? + + +### Please provide any additional information below. + +[[!format sh """ +# If you can, paste a complete transcript of the problem occurring here. +# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log + + +# End of transcript or log. +"""]] diff --git a/doc/bugs/Automatic_upgrades_should_be_cryptographically_signed/comment_1_37ed871c82879a31c2d8cfc7d9736548._comment b/doc/bugs/Automatic_upgrades_should_be_cryptographically_signed/comment_1_37ed871c82879a31c2d8cfc7d9736548._comment new file mode 100644 index 000000000..8deae448c --- /dev/null +++ b/doc/bugs/Automatic_upgrades_should_be_cryptographically_signed/comment_1_37ed871c82879a31c2d8cfc7d9736548._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.87" + subject="comment 1" + date="2013-12-11T06:20:57Z" + content=""" +The links to the builds use https. The automatic upgrades use https (and wget or curl, which will reject an invalid SSL certificate). + +So, it is cryptographically signed. Of course SSL certificates are only as secure as the CAs. But using a gpg key that most users have no particular reason to trust would not add a lot of security. +"""]] |