From ff98fe77190b331e9d1d87ae46c03e96228faf27 Mon Sep 17 00:00:00 2001
From: "http://joeyh.name/" <joey@web>
Date: Thu, 23 May 2013 20:04:03 +0000
Subject: Added a comment

---
 .../S3/comment_10_c366f020c9b97a365e21878a33360079._comment    | 10 ++++++++++
 1 file changed, 10 insertions(+)
 create mode 100644 doc/special_remotes/S3/comment_10_c366f020c9b97a365e21878a33360079._comment

(limited to 'doc/special_remotes')

diff --git a/doc/special_remotes/S3/comment_10_c366f020c9b97a365e21878a33360079._comment b/doc/special_remotes/S3/comment_10_c366f020c9b97a365e21878a33360079._comment
new file mode 100644
index 000000000..bc06156cf
--- /dev/null
+++ b/doc/special_remotes/S3/comment_10_c366f020c9b97a365e21878a33360079._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ nickname="joey"
+ subject="comment 10"
+ date="2013-05-23T20:04:03Z"
+ content="""
+You can enable a special remote on a clone by running `git annex enableremote $name`, where $name is the name you used to originally create the special remote. (Older versions of git-annex used `git annex initremote` to enable the special remote on the clone.)
+
+(Just in case, I have verified that embedcreds does cause the cipher= to be stored in the remote.log. It does.)
+"""]]
-- 
cgit v1.2.3