From b0cae9946a09a11aaaf83eceb924e0e1ca44b33f Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlgyVag95OnpvSzQofjyX0WjW__MOMKsl0" Date: Wed, 28 Nov 2012 11:47:46 +0000 Subject: [PATCH] --- ...ithin_the_repo_without_copying___63__.mdwn | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 doc/forum/Moving_large_files_within_the_repo_without_copying___63__.mdwn diff --git a/doc/forum/Moving_large_files_within_the_repo_without_copying___63__.mdwn b/doc/forum/Moving_large_files_within_the_repo_without_copying___63__.mdwn new file mode 100644 index 0000000000..55d51f21df --- /dev/null +++ b/doc/forum/Moving_large_files_within_the_repo_without_copying___63__.mdwn @@ -0,0 +1,19 @@ +Is there a way to move a large file without "git annex unlock"ing it (Which takes very long for copying and then rehashing the file)? +Using a simple "mv" or "git mv" results in broken symlinks, if the target directory is on a different hierarchy level: + +Example: + +Initial State: + + $ ls -Hl Pictures: + Pictures/showImages.jpg -> ../.git/annex/objects/90/32/SHA1-s8737--a8bfb285d0ae394cb75c86f1eb9f703fb678a51e/SHA1-s8737--a8bfb285d0ae394cb + +Move: + + $ mv Pictures/showImages.jpg . + +Result: + + $ ls -H showImages.jpg + ls: cannot access showImages.jpg: No such file or directory +