From f4b530839e9c6e61298cdf98a6e3b04c8aeee3c5 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U" Date: Thu, 11 Jul 2013 11:44:03 +0000 Subject: [PATCH] --- ..._fix__96___run_on_non-annexed_files_is_no-op.mdwn | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op.mdwn diff --git a/doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op.mdwn b/doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op.mdwn new file mode 100644 index 0000000000..f0a2553fdc --- /dev/null +++ b/doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op.mdwn @@ -0,0 +1,12 @@ +### Please describe the problem. + +`git annex fix` only works on files that have been annexed, already. +While that's a safety measure of course, an option like `--force` or similar would be nice if one is shuffling around data by hand. + +### What steps will reproduce the problem? + +Please see [[bugs/__96__git_annex_add__96___changes_mtime_if_symlinks_are_fixed_in_the_background/]] for details; I didn't want to spam exactly the same output twice. + +### What version of git-annex are you using? On what operating system? + +git-annex 4.20130709 on Debian unstable i386 and x64.