From e8575fd3b0b204539deef5780fefb3146c12e547 Mon Sep 17 00:00:00 2001 From: mario Date: Sat, 13 Apr 2019 21:43:14 +0000 Subject: [PATCH] --- doc/forum/copy_symlinks.mdwn | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/forum/copy_symlinks.mdwn diff --git a/doc/forum/copy_symlinks.mdwn b/doc/forum/copy_symlinks.mdwn new file mode 100644 index 0000000000..5f74994742 --- /dev/null +++ b/doc/forum/copy_symlinks.mdwn @@ -0,0 +1,11 @@ +Hi, + +I'm always confused when I try to copy a file within an annex repository. I know that I can just copy the symlink, so I don't have to move the actual data around. But what do I do with the new symlink: "git add" or "git annex add"? And what happens when I do the wrong one? + +Since "git annex add FILE" usually creates a symlink to FILE (and then git add on the symlink) I wonder if I'll end up with a symlink to a symlink. Would be somehow logical but pretty confusing. + +So I think both "git add LINK" and "git annex add LINK" should behave identical when LINK is a copy of symlink of an annexed file. However, this would still be confusing, since one would not expect that both commands behave identical in some situations but different in other situations. + +So, what's the best way to copy an already annexed file (destination in the same repository)? + +Best, Mario