From a5559393686b37093728a5c1dafc8abc79ee9188 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 9 Apr 2015 13:42:28 -0400 Subject: moreinfo needed --- ...ent_1_9f248d82f93040b739b56515d18458c7._comment | 24 ++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 doc/bugs/corrupt_backend_upon_sync__63__/comment_1_9f248d82f93040b739b56515d18458c7._comment diff --git a/doc/bugs/corrupt_backend_upon_sync__63__/comment_1_9f248d82f93040b739b56515d18458c7._comment b/doc/bugs/corrupt_backend_upon_sync__63__/comment_1_9f248d82f93040b739b56515d18458c7._comment new file mode 100644 index 000000000..ddec07c1e --- /dev/null +++ b/doc/bugs/corrupt_backend_upon_sync__63__/comment_1_9f248d82f93040b739b56515d18458c7._comment @@ -0,0 +1,24 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-04-09T17:39:28Z" + content=""" +The symink that you're showing is a file checked into git. + +So, you should be able to run `git log 'Pictures/2014/06/21/2014-06-21 13.52.34.png'` +on the remote and find a commit that somehow changed the symlink to the +broken one that the remote has. + +The only other possibilities are + +* Somehow the data in git in the remote got corrupted, and git didn't + notice. Seems very unlikely. +* Somehow git decided to munge up the symlink when checking it out on the + remote. While there are some git features like smudge filters that could + perhaps be configured to do that, I don't see how git could do it on its + own. + +I've never seen git do anything like this. +You're going to have to investigate this on your own and/or provide enough +information to reproduce the problem. +"""]] -- cgit v1.2.3