From f7f831e2a3e42017e124b35796fc9be3605c6b5f Mon Sep 17 00:00:00 2001 From: anarcat Date: Sat, 2 Dec 2017 00:26:29 +0000 Subject: note when the command was introduced --- doc/git-annex-export.mdwn | 4 ++++ 1 file changed, 4 insertions(+) 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 -- cgit v1.2.3 From 6dfa06522ace4e37f1358fa9a4106fbe3e35db2e Mon Sep 17 00:00:00 2001 From: "http://xgm.de/oid/" Date: Mon, 4 Dec 2017 20:04:56 +0000 Subject: --- doc/forum/What_does_a___91__RepoName__93___means__63__.mdwn | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 doc/forum/What_does_a___91__RepoName__93___means__63__.mdwn 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! -- cgit v1.2.3 From 8aaa367f27c3ef30db8db2815331ad229b922735 Mon Sep 17 00:00:00 2001 From: andrew Date: Tue, 5 Dec 2017 13:49:42 +0000 Subject: Added a comment: gcrypt, git-annex and rsync requires absolute path --- .../comment_7_2ad1079ba07013fbb8adabc673042a8f._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest/comment_7_2ad1079ba07013fbb8adabc673042a8f._comment 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. +"""]] -- cgit v1.2.3