From 95d43cf5eed53f26b50d66f6672b02ca533e9342 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 15 Jan 2016 15:12:50 -0400 Subject: [PATCH] response --- ...nt_2_54a1811ef2f57f0843e48572ab6713b8._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/tips/unlocked_files/comment_2_54a1811ef2f57f0843e48572ab6713b8._comment diff --git a/doc/tips/unlocked_files/comment_2_54a1811ef2f57f0843e48572ab6713b8._comment b/doc/tips/unlocked_files/comment_2_54a1811ef2f57f0843e48572ab6713b8._comment new file mode 100644 index 0000000000..83788d4794 --- /dev/null +++ b/doc/tips/unlocked_files/comment_2_54a1811ef2f57f0843e48572ab6713b8._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2016-01-15T19:07:24Z" + content=""" +Direct mode is not going away any time soon. + +`git add` adds the file to the annex in unlocked mode, and `git annex sync` +commits any such adds the same as any other changes, so all you need is +`git add --all; git annex sync --content` + +Whether a file is locked or unlocked is a property of the file, that gets +committed to git, so when you commit some unlocked files, they'll be +unlocked when they appear in other clones of the repository. +"""]]