comment

diff --git a/doc/design/exporting_trees_to_special_remotes.mdwn b/doc/design/exporting_trees_to_special_remotes.mdwn
index 5d6746f5b2088a0dcf166edb50ec8942b0b5e245..f786af2cf5314f9d70624b9d2245b9af0133a757 100644 (file)
--- a/doc/design/exporting_trees_to_special_remotes.mdwn
+++ b/doc/design/exporting_trees_to_special_remotes.mdwn
@@ -2,8 +2,6 @@ For publishing content from a git-annex repository, it would be useful to
 be able to export a tree of files to a special remote, using the filenames
 and content from the tree.
 
-(See also [[todo/export]] and [[todo/dumb, unsafe, human-readable_backend]])
-
 Note that this document was written with the assumption that only git-annex
 is writing to the special remote. But
 [[importing_trees_from_special_remotes]] invalidates that assumption,

diff --git a/doc/forum/Making_git-annex_preserve_file_name__44___and_directory/comment_4_2c36e30b3e2f6874c63e03307207a6b9._comment b/doc/forum/Making_git-annex_preserve_file_name__44___and_directory/comment_4_2c36e30b3e2f6874c63e03307207a6b9._comment
new file mode 100644 (file)
index 0000000..fc29013
--- /dev/null
+++ b/doc/forum/Making_git-annex_preserve_file_name__44___and_directory/comment_4_2c36e30b3e2f6874c63e03307207a6b9._comment
@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 4"""
+ date="2022-05-02T18:35:56Z"
+ content="""
+See this issue:
+<https://github.com/DanielDent/git-annex-remote-rclone/issues/35>
+
+That also has some discussion about git-annex-remote-googledrive 
+seeming to not be allowed by google and how to get around that problem.
+"""]]