From 91b2285010e4cf3dff86dd0c633eb1a7807475e5 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 4 Apr 2022 12:18:05 -0400 Subject: [PATCH] comment --- ...ent_1_fc127bc73c650404df4f21c9a04b3dd4._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/todo/Split_autocommit_option/comment_1_fc127bc73c650404df4f21c9a04b3dd4._comment diff --git a/doc/todo/Split_autocommit_option/comment_1_fc127bc73c650404df4f21c9a04b3dd4._comment b/doc/todo/Split_autocommit_option/comment_1_fc127bc73c650404df4f21c9a04b3dd4._comment new file mode 100644 index 0000000000..f4862bed16 --- /dev/null +++ b/doc/todo/Split_autocommit_option/comment_1_fc127bc73c650404df4f21c9a04b3dd4._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2022-04-04T16:10:21Z" + content=""" +remote.name.annex-sync controls #2 + +I don't think it makes sense for different git-annex commands that do +substantially the same thing to have different options to control that +thing. So I do not see why annex.autocommit should not be used by both the +assistant and git-annex sync. If you need to run one command with the +option set and another with the option unset, there are ways to do that, eg +a shell script or git alias. +"""]]