summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar mark@6b90344cdab3158eacb94a3944460d138afc9bef <mark@web>2016-03-10 22:46:42 +0000
committerGravatar admin <admin@branchable.com>2016-03-10 22:46:42 +0000
commit42ef47f99c1acda30d16c3c6cc6317945929a2da (patch)
tree7e075bc667f570658e290d422f053f7c9e6be993
parent73bdd1a37b62123238b6c107f0a6fba6c5923c57 (diff)
-rw-r--r--doc/bugs/Git_copy_fails_with_absolute_path_on_mavericks.mdwn12
1 files changed, 12 insertions, 0 deletions
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!