From 5581dc3318334627ae7979936b3fc02c0f1a1fa4 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 22 Oct 2019 13:30:04 -0400 Subject: [PATCH] comment --- ...1_affdfd11cee2c6bfe5a2ed434708ee64._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/todo/separate_annex.largefiles.git-add_and_annex.largefiles.git-annex-add_settings/comment_1_affdfd11cee2c6bfe5a2ed434708ee64._comment diff --git a/doc/todo/separate_annex.largefiles.git-add_and_annex.largefiles.git-annex-add_settings/comment_1_affdfd11cee2c6bfe5a2ed434708ee64._comment b/doc/todo/separate_annex.largefiles.git-add_and_annex.largefiles.git-annex-add_settings/comment_1_affdfd11cee2c6bfe5a2ed434708ee64._comment new file mode 100644 index 0000000000..12983b2d88 --- /dev/null +++ b/doc/todo/separate_annex.largefiles.git-add_and_annex.largefiles.git-annex-add_settings/comment_1_affdfd11cee2c6bfe5a2ed434708ee64._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2019-10-22T17:23:54Z" + content=""" +I am not convinced that making this configurable does anything other than +give users a new way to shoot themselves in their foot, and adding another +config setting I have to tease out of them in the ensuring bug report. + +My comment on [[forum/lets_discuss_git_add_behavior]] describes scenarios +where such a git add behavior would result in accidentially adding large +files to the git object store. + +The only way that would seem to avoid that is a config setting that +disables all support for populating annexed unlocked files, as well as +making git-add not smudge them, so the repository is basically treated +just like a v5 repository. +"""]]