From 42ef47f99c1acda30d16c3c6cc6317945929a2da Mon Sep 17 00:00:00 2001 From: "mark@6b90344cdab3158eacb94a3944460d138afc9bef" Date: Thu, 10 Mar 2016 22:46:42 +0000 Subject: --- doc/bugs/Git_copy_fails_with_absolute_path_on_mavericks.mdwn | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/Git_copy_fails_with_absolute_path_on_mavericks.mdwn diff --git a/doc/bugs/Git_copy_fails_with_absolute_path_on_mavericks.mdwn b/doc/bugs/Git_copy_fails_with_absolute_path_on_mavericks.mdwn new file mode 100644 index 000000000..5704bf1cc --- /dev/null +++ b/doc/bugs/Git_copy_fails_with_absolute_path_on_mavericks.mdwn @@ -0,0 +1,12 @@ +### Please describe the problem. + +git-annex version: 6.20160126 + +Problem happens on Mavericks, not on Yosemite with same version. + +Can do a relative or absolute path on a git annex add. + +But on the git annex copy to an S3 remote, if I use an absolute path for the file descriptor (e.g. /Users/name/git_directory/test.txt) it will not report an error, but will also not print the "copied..." string. A subsequent call with a relative path (e.g. test.txt) will work, show the copied message and indeed show up on S3. + + +Good news: It's working great on Yosemite! -- cgit v1.2.3