From 36d68a8f0a6fa2808d872d776f246d458681a192 Mon Sep 17 00:00:00 2001 From: "http://christian.amsuess.com/chrysn" Date: Fri, 7 Oct 2016 09:11:56 +0000 Subject: [PATCH] Added a comment: Re: attaching a torrent file to a downloaded and annexed directory --- .../comment_2_bccc7409111e4df4f4aab3b21fa4d321._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/special_remotes/bittorrent/comment_2_bccc7409111e4df4f4aab3b21fa4d321._comment diff --git a/doc/special_remotes/bittorrent/comment_2_bccc7409111e4df4f4aab3b21fa4d321._comment b/doc/special_remotes/bittorrent/comment_2_bccc7409111e4df4f4aab3b21fa4d321._comment new file mode 100644 index 0000000000..56ac48bcce --- /dev/null +++ b/doc/special_remotes/bittorrent/comment_2_bccc7409111e4df4f4aab3b21fa4d321._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://christian.amsuess.com/chrysn" + nickname="chrysn" + subject="Re: attaching a torrent file to a downloaded and annexed directory" + date="2016-10-07T09:11:55Z" + content=""" +wzhd, you can do `git annex addurl file:///full/path/to/file.torrent`. this has the downside of denoting a local file that may vanish or not be present at the same location in another checkout, but then again, same goes for http uris. (i'd rather like the torrent file or at least the info part thereof present in git or git-annex; adding the torrent with `addurl --raw` and then using its `file://` url at least gives all the data needed to use the torrent again). +"""]]