3 subject="""comment 2"""
4 date="2017-04-07T16:58:42Z"
6 Huh, so it seems that for gcrypt remotes, enableremote just doesn't
7 call their setup function at all!
9 Ah, it's because it sees the remote has an url, so it is not treated
10 as a special remote, but as a regular git remote, and so the
11 special remote encryption changes are ignored. (Since 6.20160527)
13 So, enableremote needs to fail when it thinks it's enabling a regular git
14 remote and has been passed some parameters which cannot apply to such a
17 And, enableremote needs fixed to treat existing gcrypt remotes as special
20 Also, gcrypt special remotes didn't actually support being re-enabled
21 either. I made that work. When an encryption key is added, that
22 automatically makes it change the gcrypt-participants, too.
24 I suppose enableremote could even be made to do the `GCRYPT_FULL_REPACK`
25 and forced push, but that seems like too much for it to do!