From: Joey Hess Date: Mon, 2 May 2022 18:45:45 +0000 (-0400) Subject: comment X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~1^2~75^2~8 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=37dea232a4f65e95906d45aa6d47b8a50eec380d;p=git-annex.git comment --- diff --git a/doc/design/exporting_trees_to_special_remotes.mdwn b/doc/design/exporting_trees_to_special_remotes.mdwn index 5d6746f5b2..f786af2cf5 100644 --- 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 index 0000000000..fc290138c0 --- /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: + + +That also has some discussion about git-annex-remote-googledrive +seeming to not be allowed by google and how to get around that problem. +"""]]