Added a comment
authoryarikoptic <yarikoptic@web>
Mon, 21 Feb 2022 21:53:03 +0000 (21:53 +0000)
committeradmin <admin@branchable.com>
Mon, 21 Feb 2022 21:53:03 +0000 (21:53 +0000)
doc/todo/annex.addunlocked_in_gitattributes/comment_4_d87e08ccdec98867dd52b629e6fad330._comment [new file with mode: 0644]

diff --git a/doc/todo/annex.addunlocked_in_gitattributes/comment_4_d87e08ccdec98867dd52b629e6fad330._comment b/doc/todo/annex.addunlocked_in_gitattributes/comment_4_d87e08ccdec98867dd52b629e6fad330._comment
new file mode 100644 (file)
index 0000000..67d8b41
--- /dev/null
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="yarikoptic"
+ avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
+ subject="comment 4"
+ date="2022-02-21T21:53:03Z"
+ content="""
+just it is getting a bit \"confusing\" to use `.gitattributes` for some types of annotations (e.g., `largefiles`) for files patterns and then `git annex config` for others.  Ideally there should either be a singular or equivalently expressive (not complimentary) multiple ways.
+
+> without the problems of using git attributes
+
+could you please remind (or point to prior composed list) of those? I personally just keep forgetting which one (first or last match) applies ;)
+"""]]