todo/config setting to force --progress reporting for some git callsyohhttp://git-annex.branchable.com/todo/config_setting_to_force_--progress_reporting_for_some_git_calls/git-annexikiwiki2020-06-17T01:18:32Zcomment 1http://git-annex.branchable.com/todo/config_setting_to_force_--progress_reporting_for_some_git_calls/comment_1_06d6dd17b7bd45b96276770b09bedca9/joey2019-01-21T15:42:51Z2018-10-03T16:27:45Z
<p>Hrm, git checkout does not have a --progress flag that I can see.
Perhaps they were thinking about git clone, which does have a progress, but
the repo is already cloned at this point.</p>
comment 2http://git-annex.branchable.com/todo/config_setting_to_force_--progress_reporting_for_some_git_calls/comment_2_d9135802f29b78749833b7fd9967cc0b/yarikoptic2019-01-21T15:42:51Z2018-10-03T17:55:04Z
<p>hm...</p>
<pre><code>$> git checkout --help | grep progress
--[no-]progress
This flag enables progress reporting even if not attached to a
$> git --version
git version 2.19.0
</code></pre>
comment 3http://git-annex.branchable.com/todo/config_setting_to_force_--progress_reporting_for_some_git_calls/comment_3_8a6027fb58c4b7aaa3f82b5fd1c2812a/joey2019-01-21T15:42:51Z2018-10-04T16:53:31Z
<p>Ah, I see, I was searching for "--progress".</p>
<p>I suppose what would make sense is to add the same option to the git-annex
commands that can do a git checkout: init, adjust, sync, view, vpop, vadd,
vcycle.</p>
comment 4http://git-annex.branchable.com/todo/config_setting_to_force_--progress_reporting_for_some_git_calls/comment_4_ceb543ebac42bf7a5f1571ff3f4ef977/joey2020-06-17T01:18:32Z2020-01-30T16:23:55Z
<p>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.</p>
<p>I don't think it makes sense to add --progress to every single
git-annex command.</p>
<p>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.</p>
comment 5http://git-annex.branchable.com/todo/config_setting_to_force_--progress_reporting_for_some_git_calls/comment_5_ec99ba117fac299fc361a32de4ff29a5/joey2020-06-17T01:18:32Z2020-01-30T16:38:30Z
<p>Heh, looking at the code, <a href="http://source.git-annex.branchable.com/?p=source.git;a=commitdiff;h=24838547e2475b37d7e910361f9b6e087a1a0648">24838547e2475b37d7e910361f9b6e087a1a0648</a> in 2018
made --progress be unconditionally passed when entering an adjusted branch.</p>
<p>That was done for unrelated reasons, but I don't think there's anything more
to do on this now.</p>