Merge branch 'master' into import-from-s3

doc/devblog/day_583__S3_import_and_export_fully_working.mdwn

@@ -0,0 +1,17 @@
+Got S3 import and export working fully for both versioned and unversioned
+buckets. This included developing a patch to the aws library; only
+versioned buckets are fully supported until that gets merged.
+
+I'm left with one blocking problem before merging `import-from-s3`: The commit
+history when importing from a versioned bucket is too long. It needs to
+find the point in the versioned import that has already been committed and
+avoid committing it again. Have started on that, but didn't get all the way
+today.
+
+Also, this S3 import feature should be able to be used with anonymous S3
+access to a bucket, and indeed that might be more common than wanting to
+import from a bucket you own or have credentials to allow access to. 
+But the S3 remote does not currently try to use anonymous S3 access,
+so supporting that will need some more changes.
+
+(Keyboard is fixed, yay!)

doc/forum/How_do_I_list_links_with_0_copies__63__/comment_4_61a441f83ef690da8e799b0503526c47._comment

@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="avar"
+ avatar="http://cdn.libravatar.org/avatar/57332d67a86eb51e06bf78d2baf42c3c"
+ subject="A useful command in combination with this"
+ date="2019-04-24T12:37:35Z"
+ content="""
+I've found this useful in combination with this:
+
+```
+git annex find --copies 1 --and --in=NAME --print0 | xargs -0 git annex drop --force
+```
+
+Where `NAME` is some remote of \"incoming downloads\". If nobody's fetched stuff from it let's just \"drop\" it. Running this before the command Joey suggested is best.
+"""]]