From 459c10a436c73be57bf8f87ceeacd9a9aad21c2c Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Fri, 20 Sep 2019 18:53:03 +0000 Subject: [PATCH] Added a comment: meanwhile --- ...ment_6_11b1fa357953736925cfbbc1079590dd._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/git-annex-metadata/comment_6_11b1fa357953736925cfbbc1079590dd._comment diff --git a/doc/git-annex-metadata/comment_6_11b1fa357953736925cfbbc1079590dd._comment b/doc/git-annex-metadata/comment_6_11b1fa357953736925cfbbc1079590dd._comment new file mode 100644 index 0000000000..e199e4f059 --- /dev/null +++ b/doc/git-annex-metadata/comment_6_11b1fa357953736925cfbbc1079590dd._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="meanwhile" + date="2019-09-20T18:53:03Z" + content=""" +I am [thinking about some abominations](https://github.com/datalad/datalad/issues/3696) to workaround inability to specify smth like + +``` +licenses/* annex.commit.metadata=(distribution-restrictions=sensitive) +``` +in `.gitattributes`. IMHO by limiting to `.commit` the scope when annex should add metadata becomes clear. Sure thing it could leak across files with the same content (0-length files are most prone) but it is unrelated IMHO since a direct call to `git annex metadata licenses/* -s ...` would have the same effect anyways. +"""]]