mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

thought

Browse source
This commit is contained in:
Joey Hess 2019-10-10 12:06:37 -04:00
parent 212abec4b2
commit d9938b97c6
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 24 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
doc/todo/support_multiple_special_remotes_with_same_uuid/comment_11_35e79b18923ef1c8cb8473b849262955._comment Normal file
View file

@ -0,0 +1,24 @@
[[!comment format=mdwn
username="joey"
subject="""comment 11"""
date="2019-10-10T15:49:20Z"
content="""
Comment 6 talked about how to prevent old git-annex from getting confused
when used in a repo with sameas remotes.
If remote.name.annex-uuid contains the uuid that sameas pointed to, then
old git-annex will load the RemoteConfig for that uuid. Which is kind of
... ok? The other gitconfig settings for the remote may or may not work
with that RemoteConfig. But if accessing that remote fails with old
git-annex, no problem. The only concerning thing I think would be if
checkpresent somehow reported all content as missing from the remote... But
if a misconfiguration of the gitconfig can do that, the special remote
implementation is arguably already buggy.
So, I think it's ok to set remote.name.annex-uuid to the sameas
uuid. There will need to be a new config key that indicates the uuid to
get the RemoteConfig from.
Old git-annex enableremote still needs to be prevented from initializing a
sameas remote, as it would set annex-uuid to the wrong uuid.
"""]]