From 711f1e26bb8032a55a25ee31b7a95d530732b273 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 7 Nov 2017 16:22:25 -0400 Subject: [PATCH] answer --- ..._383af8e1e26e4119671437aace0a58f5._comment | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/git-annex-adjust/comment_2_383af8e1e26e4119671437aace0a58f5._comment diff --git a/doc/git-annex-adjust/comment_2_383af8e1e26e4119671437aace0a58f5._comment b/doc/git-annex-adjust/comment_2_383af8e1e26e4119671437aace0a58f5._comment new file mode 100644 index 0000000000..a0a2700954 --- /dev/null +++ b/doc/git-annex-adjust/comment_2_383af8e1e26e4119671437aace0a58f5._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2017-11-07T20:18:19Z" + content=""" +`git annex fix` fixes up the symlinks before they're committed. +It's run by the pre-commit hook, so even when annexed files are +manually moved around, the symlinks that get committed are always +right. + +So then, if the symlinks committed are always right, +how would `git annex adjust --fix` be useful? Well, +there are ways to check out git repositories that make +the .git directory not be in the usual place. For example, +when using submodules, git puts that directory in a different place. +And then the committed symlinks won't point to .git. So, +`git annex adjust --fix` is useful as a way to adjust the symlinks +locally, without committing any changes to them, in that kind of +situation. +"""]]