diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2016-09-21 13:42:42 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2016-09-21 13:42:42 -0400 |
| commit | c411c395a6968a19dda42c90f8bdd334473c642f (patch) | |
| tree | 2fd467d2a2a16fb70094aff7d3fa549041bc9e6d | |
| parent | fd1b4a78662d19816b48cf88038fb243b79d7121 (diff) | |
comment, retitle
| -rw-r--r-- | doc/bugs/autoenable__61__true_seems_to_not_work_any_longer.mdwn | 2 | ||||
| -rw-r--r-- | doc/bugs/autoenable__61__true_seems_to_not_work_any_longer/comment_1_457027471d09aa4ae8718c1508cfae1d._comment | 27 |
2 files changed, 29 insertions, 0 deletions
diff --git a/doc/bugs/autoenable__61__true_seems_to_not_work_any_longer.mdwn b/doc/bugs/autoenable__61__true_seems_to_not_work_any_longer.mdwn index 3f6a60221..86ecda2ed 100644 --- a/doc/bugs/autoenable__61__true_seems_to_not_work_any_longer.mdwn +++ b/doc/bugs/autoenable__61__true_seems_to_not_work_any_longer.mdwn @@ -75,3 +75,5 @@ I am a little confused though since we do test for this scenario in datalad and [[!meta author=yoh]] + +[[!meta title="autoenable not done for implicit init"]] diff --git a/doc/bugs/autoenable__61__true_seems_to_not_work_any_longer/comment_1_457027471d09aa4ae8718c1508cfae1d._comment b/doc/bugs/autoenable__61__true_seems_to_not_work_any_longer/comment_1_457027471d09aa4ae8718c1508cfae1d._comment new file mode 100644 index 000000000..0c8585d60 --- /dev/null +++ b/doc/bugs/autoenable__61__true_seems_to_not_work_any_longer/comment_1_457027471d09aa4ae8718c1508cfae1d._comment @@ -0,0 +1,27 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-09-21T17:37:39Z" + content=""" +`git annex init` does handle autoenable. When you bypass explicit init, +it does not do autoenabling. + +This is not a change AFAICS. The changelog entry for autoenable +says that it's done by `git annex init`. Presumably your test suite +does run `git annex init`. + +My original notes on why not to have automaitic init handle autoenable were: + +> There was also the question of what to do when git-annex auto-inits +> in a clone of a repository. It wouldn't do for a command like +> `git annex find`'s output to include any messages that might be shown +> while auto-enabling special remotes as a result of an auto-init. +> Since I can't guarantee enabling special remotes will be quiet, I've not +> tried to auto-enable special remotes in this case. +> +> I think I'd have to +> exec a git-annex init process with stdout sent to stderr to implement +> this in a safe way, and due to calls to ensureInitialized in Remote.Git, +> which can auto-init a local remote, that gets particularly tricky. Best, +> I feel, to wait and see if anyone needs that. +"""]] |