From e2ac9cf521df52777de92611b07b256a0844cf7d Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 30 Jan 2020 12:40:39 -0400 Subject: [PATCH] already fixed --- ...--progress_reporting_for_some_git_calls.mdwn | 3 ++- ..._4_ceb543ebac42bf7a5f1571ff3f4ef977._comment | 17 +++++++++++++++++ ..._5_ec99ba117fac299fc361a32de4ff29a5._comment | 12 ++++++++++++ 3 files changed, 31 insertions(+), 1 deletion(-) create mode 100644 doc/todo/config_setting_to_force_--progress_reporting_for_some_git_calls/comment_4_ceb543ebac42bf7a5f1571ff3f4ef977._comment create mode 100644 doc/todo/config_setting_to_force_--progress_reporting_for_some_git_calls/comment_5_ec99ba117fac299fc361a32de4ff29a5._comment diff --git a/doc/todo/config_setting_to_force_--progress_reporting_for_some_git_calls.mdwn b/doc/todo/config_setting_to_force_--progress_reporting_for_some_git_calls.mdwn index 24c6e52de6..fea3e171a8 100644 --- a/doc/todo/config_setting_to_force_--progress_reporting_for_some_git_calls.mdwn +++ b/doc/todo/config_setting_to_force_--progress_reporting_for_some_git_calls.mdwn @@ -6,4 +6,5 @@ Thanks in advance for considering [[!meta author=yoh]] [[!tag projects/datalad]] -[[!tag confirmed]] + +> [[done]] diff --git a/doc/todo/config_setting_to_force_--progress_reporting_for_some_git_calls/comment_4_ceb543ebac42bf7a5f1571ff3f4ef977._comment b/doc/todo/config_setting_to_force_--progress_reporting_for_some_git_calls/comment_4_ceb543ebac42bf7a5f1571ff3f4ef977._comment new file mode 100644 index 0000000000..55b02b182c --- /dev/null +++ b/doc/todo/config_setting_to_force_--progress_reporting_for_some_git_calls/comment_4_ceb543ebac42bf7a5f1571ff3f4ef977._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2020-01-30T16:23:55Z" + content=""" +Occurs to me that any git-annex command could result in an automatic +init, and since v7 is default, will enter an adjusted branch when on a +crippled filesystem. + +I don't think it makes sense to add --progress to every single +git-annex command. + +I suppose, if your code always runs git-annex init after clone, then it +would be good enough to have git-annex init be the only thing that +supports --progress. If something else needs it (maybe the view commands), +we can treat that separately. +"""]] diff --git a/doc/todo/config_setting_to_force_--progress_reporting_for_some_git_calls/comment_5_ec99ba117fac299fc361a32de4ff29a5._comment b/doc/todo/config_setting_to_force_--progress_reporting_for_some_git_calls/comment_5_ec99ba117fac299fc361a32de4ff29a5._comment new file mode 100644 index 0000000000..42452649f0 --- /dev/null +++ b/doc/todo/config_setting_to_force_--progress_reporting_for_some_git_calls/comment_5_ec99ba117fac299fc361a32de4ff29a5._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 5""" + date="2020-01-30T16:38:30Z" + content=""" +Heh, looking at the code, [[!commit +24838547e2475b37d7e910361f9b6e087a1a0648]] in 2018 +made --progress be unconditionally passed when entering an adjusted branch. + +That was done for unrelated reasons, but I don't think there's anything more +to do on this now. +"""]]