From: Joey Hess <joeyh@joeyh.name>
Date: Tue, 19 Apr 2022 16:14:12 +0000 (-0400)
Subject: comment
X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~1^2~75^2~50
X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=e57a3efd1b1d969bef6be7bc61d3c8e7921cdca2;p=git-annex.git

comment
---

diff --git a/doc/git-annex-add/comment_7_bb9d72f90f4d3c93d71de1a1bbc244b6._comment b/doc/git-annex-add/comment_7_bb9d72f90f4d3c93d71de1a1bbc244b6._comment
new file mode 100644
index 0000000000..166bd2e14d
--- /dev/null
+++ b/doc/git-annex-add/comment_7_bb9d72f90f4d3c93d71de1a1bbc244b6._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 7"""
+ date="2022-04-19T16:09:12Z"
+ content="""
+@lh I don't feel this man page's comment section is the place to discuss
+this in detail. But suffice to say that even if add behaved the way you
+suggest, any other git-annex command can commit the accumulated changes
+to the git-annex branch at any time. So the change would not guarantee
+the behavior you hope for.
+
+But, you can set annex.alwayscommit to false and run `git-annex merge`
+when you do want to commit changes to the git-annex branch.
+"""]]