From 6b9478a1cd72432e8da8978a905526c915f859ad Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 27 Mar 2015 15:35:46 -0400 Subject: comment --- ...ent_3_a0fdcd19954a38141b1dc2a51638ba30._comment | 24 ++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 doc/forum/Adding_files_with_wildcard_on_Mac_Yosemite/comment_3_a0fdcd19954a38141b1dc2a51638ba30._comment diff --git a/doc/forum/Adding_files_with_wildcard_on_Mac_Yosemite/comment_3_a0fdcd19954a38141b1dc2a51638ba30._comment b/doc/forum/Adding_files_with_wildcard_on_Mac_Yosemite/comment_3_a0fdcd19954a38141b1dc2a51638ba30._comment new file mode 100644 index 000000000..109115c9a --- /dev/null +++ b/doc/forum/Adding_files_with_wildcard_on_Mac_Yosemite/comment_3_a0fdcd19954a38141b1dc2a51638ba30._comment @@ -0,0 +1,24 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2015-03-27T19:25:26Z" + content=""" +The shell does not expand *.jpg to match files inside subdirectories. + +I suggest you read up on how shell wildcards work, and how to use them +properly. + +There is a bit of a bug here, which is that the shell, when *.jpg does not +expand to anything, passes the "*.jpg" parameter to git-annex un-expanded, +which then passes it off to git ls-files, which then unexpectedly expands +it to recursively match jpegs in subirectories. Only then does git-annex +try to add a "*.jpg" file, and when it doesn't exist, it exits with an +error, leaving the files it did add unstaged in git. + +To get out of that situation, just re-run git-annex add and actually list +the files or directories to add, rather than a wildcard that won't expand +to them.. + +I'll see if I can fix the behavior here, it should just fail when given an +un-expanded wildcard. +"""]] -- cgit v1.2.3