summaryrefslogtreecommitdiff
path: root/doc/git-annex-unannex/comment_2_d325e4201ec2964c5633e00c473df755._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/git-annex-unannex/comment_2_d325e4201ec2964c5633e00c473df755._comment')
-rw-r--r--doc/git-annex-unannex/comment_2_d325e4201ec2964c5633e00c473df755._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/git-annex-unannex/comment_2_d325e4201ec2964c5633e00c473df755._comment b/doc/git-annex-unannex/comment_2_d325e4201ec2964c5633e00c473df755._comment
new file mode 100644
index 000000000..9cec18a0b
--- /dev/null
+++ b/doc/git-annex-unannex/comment_2_d325e4201ec2964c5633e00c473df755._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2016-10-26T17:53:23Z"
+ content="""
+The behavior your comment describes is only the case with v5
+repoitories in indirect mode. With v5 direct mode repositories and
+with the newer v6 repository format, `git annex unannex`
+is able to safely handle files that have been added and not committed yet.
+"""]]