mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2019-10-21 14:50:04 -04:00
parent 869933877a
commit b2880f045b
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 19 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
doc/forum/unable_to_access_remotes_when_cloning_a_gcrypt_remote/comment_2_3623a37d918d08e8681276206137f5af._comment Normal file
View file

@ -0,0 +1,19 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2019-10-21T18:36:16Z"
content="""
I tried following the process given in that tip, and it works as it's
supposed to.
The easiest way to reproduce the error message you've reported is:
Is "path_to_repo" a unix path, with slashes in it?
It's hard for me to understand if you've obfuscated that,
or if you literally used the string "path_to_repo" there.
A complete un-edited transcript would clarify things a lot.
A repository url tells git or git-annex *where* to access a repository.
A repository's uuid tells git-annex *which* repository it is.
"""]]