From 82dadea20f58ff830fae609376300e5706c76b63 Mon Sep 17 00:00:00 2001 From: Marco Date: Mon, 8 Jun 2015 15:45:15 +0000 Subject: [PATCH] Added a comment: Once again --- ...t_4_eb5b0f8259d861000510fcfd58f66617._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/bugs/OSX:_Assistant_leaves_repo_in_inconsistent_state/comment_4_eb5b0f8259d861000510fcfd58f66617._comment diff --git a/doc/bugs/OSX:_Assistant_leaves_repo_in_inconsistent_state/comment_4_eb5b0f8259d861000510fcfd58f66617._comment b/doc/bugs/OSX:_Assistant_leaves_repo_in_inconsistent_state/comment_4_eb5b0f8259d861000510fcfd58f66617._comment new file mode 100644 index 0000000000..395c31b948 --- /dev/null +++ b/doc/bugs/OSX:_Assistant_leaves_repo_in_inconsistent_state/comment_4_eb5b0f8259d861000510fcfd58f66617._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="Marco" + subject="Once again" + date="2015-06-08T15:45:15Z" + content=""" +I was using the assistant on two machines in parallel and both git repositories got broken. Before that I was just using the command line tools and just one assistant. Today the history got inconsistent when firing up the second assistant. + +Repos in use: +- client 1 with active assistant +- client 2 with active assistant +- Synology NAS with git-annex installed (armel-based) + +I could recover everything pretty fast by cloning again from the nas device. Copying the .git/config and moving over the .git/annex directory. + +I will send you the log-files via mail. +"""]]