summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://alan.petitepomme.net/ <Alan_Schmitt@web>2014-06-05 12:05:40 +0000
committerGravatar admin <admin@branchable.com>2014-06-05 12:05:40 +0000
commite1d682e4498e508c58121a34c22559460e1083e8 (patch)
treeea93184f341456b99aee328036532bf828219fc0
parenta0175b85e8b24c4014e881a9f2e4222a7359c0b7 (diff)
Added a comment: How is the binary found on the server?
-rw-r--r--doc/videos/git-annex_assistant_lan/comment_1_df8c8b6d9d63fbf5462b225edbb23c82._comment8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/videos/git-annex_assistant_lan/comment_1_df8c8b6d9d63fbf5462b225edbb23c82._comment b/doc/videos/git-annex_assistant_lan/comment_1_df8c8b6d9d63fbf5462b225edbb23c82._comment
new file mode 100644
index 000000000..8c67a5cfb
--- /dev/null
+++ b/doc/videos/git-annex_assistant_lan/comment_1_df8c8b6d9d63fbf5462b225edbb23c82._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="http://alan.petitepomme.net/"
+ nickname="Alan Schmitt"
+ subject="How is the binary found on the server?"
+ date="2014-06-05T12:05:40Z"
+ content="""
+Great screencast! There is one thing that intrigues me: since you simply uncompress the binary in some folder, how does gitannex figures out where the binary lives there?
+"""]]