diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2017-12-05 12:44:11 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2017-12-05 12:44:11 -0400 |
| commit | bdbd2a3cac8a4054a32f16ef322111b17ff20e06 (patch) | |
| tree | 33231fa2d24e403e24d904304228210f9e896560 | |
| parent | 5b7fe70fce652dbc83ce1baff0379b23cc8bb5b2 (diff) | |
| parent | 8aaa367f27c3ef30db8db2815331ad229b922735 (diff) | |
Merge branch 'master' of ssh://git-annex.branchable.com
3 files changed, 17 insertions, 0 deletions
diff --git a/doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest/comment_7_2ad1079ba07013fbb8adabc673042a8f._comment b/doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest/comment_7_2ad1079ba07013fbb8adabc673042a8f._comment new file mode 100644 index 000000000..b02478766 --- /dev/null +++ b/doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest/comment_7_2ad1079ba07013fbb8adabc673042a8f._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="andrew" + avatar="http://cdn.libravatar.org/avatar/acc0ece1eedf07dd9631e7d7d343c435" + subject="gcrypt, git-annex and rsync requires absolute path" + date="2017-12-05T13:49:42Z" + content=""" +I struggled to get git-annex sync working for some time with gcrypt and the rsync transport protocol. It turns out I was using a relative path to my repo instead of an absolute path. In my .git/config with a url like this: `gcrypt::rsync://username@servername:relative-path-to-git-repo` where relative path is relative to my user's home directory, git push would work fine, but git-annex sync would complain it couldn't find the repository. Changing my url to an absolute path like `gcrypt::rsync://username@servername:absolute-path-to-git-repo` now allows both git-annex sync and git push to work. Andrew. +"""]] diff --git a/doc/forum/What_does_a___91__RepoName__93___means__63__.mdwn b/doc/forum/What_does_a___91__RepoName__93___means__63__.mdwn new file mode 100644 index 000000000..fa1841f69 --- /dev/null +++ b/doc/forum/What_does_a___91__RepoName__93___means__63__.mdwn @@ -0,0 +1,5 @@ +Hello, + +sometimes, ```git annex info``` shows a (special remote) repository's name in [Brackets], sometimes not. Every theory (depending on enabled / not enabled) I had so far, is disproved by my next step. What does it means when the name is in brackets? + +Thanks! diff --git a/doc/git-annex-export.mdwn b/doc/git-annex-export.mdwn index 0a5a5516a..a8f9f5cb3 100644 --- a/doc/git-annex-export.mdwn +++ b/doc/git-annex-export.mdwn @@ -107,6 +107,10 @@ export`, it will detect the export conflict, and resolve it. [[git-annex-sync]](1) +# HISTORY + +The `export` command was introduced in git-annex version 6.20170925. + # AUTHOR Joey Hess <id@joeyh.name> |