]> dgit.raspbian.org Git - git-annex.git/commitdiff
Added a comment
authoryarikoptic <yarikoptic@web>
Thu, 22 May 2025 18:23:36 +0000 (18:23 +0000)
committeradmin <admin@branchable.com>
Thu, 22 May 2025 18:23:36 +0000 (18:23 +0000)
doc/bugs/keeps_trying_to_commit_file_unlocked/comment_6_2f226e2bb6fcb1040ba8e645603607a1._comment [new file with mode: 0644]

diff --git a/doc/bugs/keeps_trying_to_commit_file_unlocked/comment_6_2f226e2bb6fcb1040ba8e645603607a1._comment b/doc/bugs/keeps_trying_to_commit_file_unlocked/comment_6_2f226e2bb6fcb1040ba8e645603607a1._comment
new file mode 100644 (file)
index 0000000..972b2b2
--- /dev/null
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="yarikoptic"
+ avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
+ subject="comment 6"
+ date="2025-05-22T18:23:36Z"
+ content="""
+Somewhat unrelated and I feel like I might have even proposed smth like that -- wouldn't it be useful if git-annex did add its version and potentially filesystem detail (if cheaply known) within its commit message to `git-annex` branch?  unless `annex forgotten` later (and forgetting could summarize all the versions and filesystems used to that point), could have been useful here, or not?
+
+FWIW, sent a few related questions on versions etc to the author of the commit which introduced that file.
+"""]]