From 2a6e12c7e27cc1ec52980e0895ae985f2b3ddd53 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 13 Aug 2015 17:34:13 -0400 Subject: followup --- .../comment_1_0724d70364f7067d864a80a39e2e609a._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/bugs/git-annex_get_with_umlaut_characters_in_filenames/comment_1_0724d70364f7067d864a80a39e2e609a._comment (limited to 'doc') diff --git a/doc/bugs/git-annex_get_with_umlaut_characters_in_filenames/comment_1_0724d70364f7067d864a80a39e2e609a._comment b/doc/bugs/git-annex_get_with_umlaut_characters_in_filenames/comment_1_0724d70364f7067d864a80a39e2e609a._comment new file mode 100644 index 000000000..b5e8f21f5 --- /dev/null +++ b/doc/bugs/git-annex_get_with_umlaut_characters_in_filenames/comment_1_0724d70364f7067d864a80a39e2e609a._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-08-13T21:29:41Z" + content=""" +`git annex get` only acts on files that are present in the working tree of +the git repo, and which `git ls-files` lists. So, if git is somehow +confused about these filenames, which is appears to be, it makes sense that +git-annex wouldn't be operating on them. + +I don't know why git would have such a problem with files with umlaut in +their names. AFAIK, git is quite agnostic about filename encodings. +However, your git status seems to be the smoking gun; the files are either +not known to git at all, or it thinks they were renamed. Does the git +log --stat show the files being deleted. Have you tried (re)adding the +files to git? +"""]] -- cgit v1.2.3