summaryrefslogtreecommitdiff
path: root/doc/special_remotes/S3
diff options
context:
space:
mode:
authorGravatar basak <basak@web>2013-05-22 18:32:05 +0000
committerGravatar admin <admin@branchable.com>2013-05-22 18:32:05 +0000
commite8f0191e063f8b5a9ad4448a79e23b87178c2adf (patch)
tree7a8a944aef8c0fb82f938af7475494511e2c8fc0 /doc/special_remotes/S3
parentd8a07041c640942e68052514b91488d55ad3a5a0 (diff)
Added a comment: Recovering from a clone
Diffstat (limited to 'doc/special_remotes/S3')
-rw-r--r--doc/special_remotes/S3/comment_9_7ad757b3865b04967c79af0a263bb3b0._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/special_remotes/S3/comment_9_7ad757b3865b04967c79af0a263bb3b0._comment b/doc/special_remotes/S3/comment_9_7ad757b3865b04967c79af0a263bb3b0._comment
new file mode 100644
index 000000000..51b7ab16a
--- /dev/null
+++ b/doc/special_remotes/S3/comment_9_7ad757b3865b04967c79af0a263bb3b0._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="basak"
+ ip="2001:8b0:1c8::2"
+ subject="Recovering from a clone"
+ date="2013-05-22T18:32:05Z"
+ content="""
+How do I recover a special remote from a clone, please? I see that `remote.log` has most of the details, but my remote is not configured on my clone and I see no obvious way to do it. And I used `embedcreds`, but the only credentials I can see are stored in .git/annex/creds/ so did not survive a clone. I'm confused because the documentation here for `embedcreds` says that clones should have access.
+
+As a workaround, it looks like copying the remote over from `.git/config` as well as the credentials from `.git/annex/creds/` seems to work. Is there some other way I'm supposed to do this, or is this the intended way?
+"""]]