From dfc68e4db7d8d4d613420a797967b05db8e9fd30 Mon Sep 17 00:00:00 2001 From: "http://edheil.wordpress.com/" Date: Fri, 8 Mar 2013 14:46:55 +0000 Subject: [PATCH] Added a comment --- ...nt_8_78e6164ef67a9560a3a9ead1f7a72473._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_8_78e6164ef67a9560a3a9ead1f7a72473._comment diff --git a/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_8_78e6164ef67a9560a3a9ead1f7a72473._comment b/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_8_78e6164ef67a9560a3a9ead1f7a72473._comment new file mode 100644 index 0000000000..c49cbbeefc --- /dev/null +++ b/doc/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/comment_8_78e6164ef67a9560a3a9ead1f7a72473._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="http://edheil.wordpress.com/" + ip="173.162.44.162" + subject="comment 8" + date="2013-03-08T14:46:55Z" + content=""" +I've not seen this kind of strange behavior happen again so far. + +But I have got another example of a file which I added to git-annex via the assistant not having its symlink added to git. Again, the content of the file is in git-annex and was even correctly transferred to a couple of remotes, but the symlink is still unstaged. + +I tried restarting the assistant to see if that would fix it but that didn't change anything. + +I imagine the symlink will be fixed during a daily scan, tomorrow maybe? Is it problematic for the symlink not to be checked into git for a day? Is this worth a bug report or is this really harmless behavior? + +"""]]