From cdab6cd9cb153050786fb197f0ce0d9f775aae8a Mon Sep 17 00:00:00 2001 From: Lukey Date: Tue, 27 Jun 2023 08:54:45 +0000 Subject: [PATCH] Added a comment --- ...comment_1_8279171695a9a7a7501d5ee8c7bab66c._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/Making_a_public_read-write_git-annex_repo/comment_1_8279171695a9a7a7501d5ee8c7bab66c._comment diff --git a/doc/forum/Making_a_public_read-write_git-annex_repo/comment_1_8279171695a9a7a7501d5ee8c7bab66c._comment b/doc/forum/Making_a_public_read-write_git-annex_repo/comment_1_8279171695a9a7a7501d5ee8c7bab66c._comment new file mode 100644 index 0000000000..349d094399 --- /dev/null +++ b/doc/forum/Making_a_public_read-write_git-annex_repo/comment_1_8279171695a9a7a7501d5ee8c7bab66c._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="Lukey" + avatar="http://cdn.libravatar.org/avatar/c7c08e2efd29c692cc017c4a4ca3406b" + subject="comment 1" + date="2023-06-27T08:54:45Z" + content=""" +Maybe a bare git repo on a nfs or smb share? I'm not sure if concurrent pushes work right with that. + +It's probably also a good idea to set `git annex config --set annex.dotfiles true`, so no one gets into a situation where they have to resolve a merge conflict manually. +"""]] -- 2.30.2