9eaabf0382
Avoid stomping on existing group and preferred content settings when enabling or combining with an already existing remote. Two level fix. First, use defaultStandardGroup rather than setStandardGroup, so if there is an existing configuration in the git-annex branch, it's not overwritten. To handle pre-existing ssh remotes (including gcrypt), a second level is needed, because before syncing with the remote, it's configuration won't be available locally. (And syncing could take a long time.) So, in this case, keep track of whether the remote is being created or enabled, and only set configs when creating it. This commit was sponsored by Anders Lannerback. |
||
|---|---|---|
| .. | ||
| AWS.hs | ||
| Delete.hs | ||
| Edit.hs | ||
| Fsck.hs | ||
| IA.hs | ||
| Local.hs | ||
| Pairing.hs | ||
| Preferences.hs | ||
| Ssh.hs | ||
| Unused.hs | ||
| Upgrade.hs | ||
| WebDAV.hs | ||
| XMPP.hs | ||