From 3efcb58b6a0652a247fcd9cf0807b601f6872fd2 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 6 Jun 2023 13:02:15 -0400 Subject: [PATCH] comment --- ..._89ea6c764e18ed4335733f979fb31140._comment | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 doc/todo/Make_addunlocked_configurable_like_largefiles/comment_2_89ea6c764e18ed4335733f979fb31140._comment diff --git a/doc/todo/Make_addunlocked_configurable_like_largefiles/comment_2_89ea6c764e18ed4335733f979fb31140._comment b/doc/todo/Make_addunlocked_configurable_like_largefiles/comment_2_89ea6c764e18ed4335733f979fb31140._comment new file mode 100644 index 0000000000..aecebf194c --- /dev/null +++ b/doc/todo/Make_addunlocked_configurable_like_largefiles/comment_2_89ea6c764e18ed4335733f979fb31140._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2023-06-06T16:50:16Z" + content=""" +You can already configure annex.addunlocked with `git-annex config`. + +Adding gitattributes for configs is problimatic because querying +for them is not fast. They have to be queried for every file. Also the +gitattributes format is not well suited to complex expressions since the +value cannot contain spaces. + +annex.addunlocked can already be set to a [[git-annex-matching-expression]] +and this allows configuring it differently for different filenames, etc. + +The only benefit to supporting it in gitattributes would be to configure it +differently in different branches of the repository. + +There was a todo already suggesting this, +[[annex.addunlocked_in_gitattributes]] and I decided to close it. +"""]]