]> dgit.raspbian.org Git - git-annex.git/commitdiff
comment
authorJoey Hess <joeyh@joeyh.name>
Wed, 15 Apr 2020 16:10:51 +0000 (12:10 -0400)
committerJoey Hess <joeyh@joeyh.name>
Wed, 15 Apr 2020 16:10:51 +0000 (12:10 -0400)
doc/bugs/commits_created_despite_alwayscommit__61__false_as_of_recent_change/comment_1_793ab4d52a3a4a3a30b0e72b72ac18eb._comment [new file with mode: 0644]

diff --git a/doc/bugs/commits_created_despite_alwayscommit__61__false_as_of_recent_change/comment_1_793ab4d52a3a4a3a30b0e72b72ac18eb._comment b/doc/bugs/commits_created_despite_alwayscommit__61__false_as_of_recent_change/comment_1_793ab4d52a3a4a3a30b0e72b72ac18eb._comment
new file mode 100644 (file)
index 0000000..9136aee
--- /dev/null
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2020-04-15T16:09:02Z"
+ content="""
+That change would lead to buggy behavior, because git-annex would then not
+commit the journal files, and the optimisation prevents it reading the
+journal files, so it would operate with out of date information.
+
+The only way to fix this, I think, is to disable the entire optimisation
+when annex.alwayscommit is set and the journal is dirty.
+"""]]