fix sameas inherited key removal
This commit is contained in:
parent
8d7dc76dff
commit
1b9c1d1737
3 changed files with 9 additions and 1 deletions
|
@ -91,4 +91,4 @@ addSameasInherited m c = case toUUID <$> M.lookup sameasUUIDField c of
|
||||||
removeSameasInherited :: RemoteConfig -> RemoteConfig
|
removeSameasInherited :: RemoteConfig -> RemoteConfig
|
||||||
removeSameasInherited c = case M.lookup sameasUUIDField c of
|
removeSameasInherited c = case M.lookup sameasUUIDField c of
|
||||||
Nothing -> c
|
Nothing -> c
|
||||||
Just _ -> M.restrictKeys c sameasInherits
|
Just _ -> M.withoutKeys c sameasInherits
|
||||||
|
|
|
@ -57,6 +57,11 @@ want to use `git annex renameremote`.
|
||||||
of the existing remote, so you should not specify any encryption
|
of the existing remote, so you should not specify any encryption
|
||||||
parameters. No other configuration is inherited from the existing remote.
|
parameters. No other configuration is inherited from the existing remote.
|
||||||
|
|
||||||
|
This will only work if both remotes use the underlying storage in
|
||||||
|
compatible ways. See this page for information about known
|
||||||
|
compatabilities.
|
||||||
|
<http://git-annex.branchable.com/tips/multiple_remotes_accessing_the_same_data_store/>
|
||||||
|
|
||||||
# COMMON CONFIGURATION PARAMETERS
|
# COMMON CONFIGURATION PARAMETERS
|
||||||
|
|
||||||
* `encryption`
|
* `encryption`
|
||||||
|
|
|
@ -34,6 +34,9 @@ the remote.log. Eg, "B sameas=A foo=bar ..."
|
||||||
|
|
||||||
Implementation notes:
|
Implementation notes:
|
||||||
|
|
||||||
|
initremote --sameas ends up with the annex-uuid and the annex-config-uuid
|
||||||
|
configured backwards. Oops.
|
||||||
|
|
||||||
Need to get enableremote working for sameas.
|
Need to get enableremote working for sameas.
|
||||||
|
|
||||||
Deal with the per-remote state issue.
|
Deal with the per-remote state issue.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue