3 subject="""comment 1"""
4 date="2016-09-21T17:37:39Z"
6 `git annex init` does handle autoenable. When you bypass explicit init,
7 it does not do autoenabling.
9 This is not a change AFAICS. The changelog entry for autoenable
10 says that it's done by `git annex init`. Presumably your test suite
11 does run `git annex init`.
13 My original notes on why not to have automaitic init handle autoenable were:
15 > There was also the question of what to do when git-annex auto-inits
16 > in a clone of a repository. It wouldn't do for a command like
17 > `git annex find`'s output to include any messages that might be shown
18 > while auto-enabling special remotes as a result of an auto-init.
19 > Since I can't guarantee enabling special remotes will be quiet, I've not
20 > tried to auto-enable special remotes in this case.
23 > exec a git-annex init process with stdout sent to stderr to implement
24 > this in a safe way, and due to calls to ensureInitialized in Remote.Git,
25 > which can auto-init a local remote, that gets particularly tricky. Best,
26 > I feel, to wait and see if anyone needs that.