From 3ce13f7a2a7e5dd4539ee43c7759bd4f3f4f30d6 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 4 Apr 2018 14:00:55 -0400 Subject: [PATCH] thoughts --- ..._215ca5e67a1bc04bcb8bea6062aebf3f._comment | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 doc/bugs/annex.genmetadata_should_default_to_true/comment_1_215ca5e67a1bc04bcb8bea6062aebf3f._comment diff --git a/doc/bugs/annex.genmetadata_should_default_to_true/comment_1_215ca5e67a1bc04bcb8bea6062aebf3f._comment b/doc/bugs/annex.genmetadata_should_default_to_true/comment_1_215ca5e67a1bc04bcb8bea6062aebf3f._comment new file mode 100644 index 0000000000..48822f22a8 --- /dev/null +++ b/doc/bugs/annex.genmetadata_should_default_to_true/comment_1_215ca5e67a1bc04bcb8bea6062aebf3f._comment @@ -0,0 +1,23 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2018-04-04T17:50:02Z" + content=""" +I think there are two potential problems with this change: + +1. Bloat. If someone is not going to use that metadata, they may not want + the overhead of attaching it to every file. + +2. It's entirely possible that a user has chosen to use year/month/day + metadata fields for their own purposes. Perhaps they are using it to + keep track of the original publication date of files, and so would not + want "wrong" values to be automatically added. + +And that's essentially the reason why all parts of git-annex that deal +with specific metadata fields are optional, so there's no default +hard-coded semantics to the metadata fields. + +(With the exception of git-annex importfeed, which always +stores the itemid from the rss feed in the metadata, but only because +it's needed to detect buggy feeds that change their item urls.) +"""]]