Merge branch 'master' of ssh://git-annex.branchable.com

doc/forum/How_to_mv_file___40__symlink__41___to_another_dir_in_the_same_repo_without_unlocking_it.mdwn

@@ -0,0 +1 @@
+This could be useful for restructuring the dir structures.

doc/forum/How_to_mv_file___40__symlink__41___to_another_dir_in_the_same_repo_without_unlocking_it/comment_1_a272d179a77682e8c64bd4fc20cddee0._comment

@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="CandyAngel"
+ avatar="http://cdn.libravatar.org/avatar/15c0aade8bec5bf004f939dd73cf9ed8"
+ subject="comment 1"
+ date="2019-01-14T12:36:04Z"
+ content="""
+You can just move it with any file manager or `git mv`.
+
+git-annex will fix the moved symlink before it is committed.
+"""]]

doc/forum/Old_versions_of_files_are_not_dropped_even_though_enough_copies_exist/comment_2_81e3664c6746fbeb2d76cca7160cf58a._comment

@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="jonas"
+ avatar="http://cdn.libravatar.org/avatar/33f6268ae24acfbdc02a1c80f6ff5e8e"
+ subject="comment 2"
+ date="2019-01-13T20:21:30Z"
+ content="""
+Thanks for the comment. I somehow forgot to mention that in my post, that `unused` does virtually nothing in this case.
+If you stop my example after the first `tree` invocation and then in the `client` repository do `git annex unused` it tells you that there are no unused files. And hence neither `dropunused` or `drop --unused` does anything more.
+
+So somehow I'm still stuck with this old version of the file which is duplicated and hence should be found and deletable, if I'm not mistaken.
+"""]]

doc/forum/Old_versions_of_files_are_not_dropped_even_though_enough_copies_exist/comment_3_d5b2b68f22796c3ecd2929f47db3601e._comment

@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="jonas"
+ avatar="http://cdn.libravatar.org/avatar/33f6268ae24acfbdc02a1c80f6ff5e8e"
+ subject="comment 3"
+ date="2019-01-13T20:40:09Z"
+ content="""
+Ok, after upgrading my repository to v7 (apparently repositories are still created as v5) git annex finds the unused versions and lets me drop them.
+"""]]

doc/forum/RecentChanges__58___link_to_the_diff__63__.mdwn

@@ -0,0 +1 @@
+In the RecentChanges page on the forum, it'd be good to have a link to the diff for the change, in addition to the existing link to the changed page.

doc/todo/add_import_--to_command.mdwn

@@ -0,0 +1,6 @@
+I have a bunch of files I want to track with `git-annex` that are sitting in an external drive. I have a repository sitting on my laptop, but I don't actually have enough free disk space on my laptop to import the files. Really, I just want the file content to be sitting in a special remote. I was thinking the following workflow could be useful:
+
+    cd ~/my-laptop-repo
+    git-annex import --to=s3-remote /mnt/usb-drive/myfiles
+
+The proposed `--to=remote` option would add the files to my repo as `import` normally does, but it wouldn't every keep the content in the repo, the only copy would now sit in `s3-remote`. As little disk space as possible would be staged temporarily in `~/my-laptop-repo`. Perhaps the easiest option would be to import a file normally, but them immediately do a `move` to `s3-remote`? But, ideally for larger files, we would want to stream them directly from `/mnt/usb-drive/myfiles` to `s3-remote` without ever staging them at `~/my-laptop-repo`.

doc/todo/add_import_--to_command/comment_1_b70d10190722c0d21c2343fe51e38414._comment

@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="Ilya_Shlyakhter"
+ avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
+ subject="comment 1"
+ date="2019-01-14T16:11:39Z"
+ content="""
+Cf. [[todo/import_tree]].
+
+"""]]