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

add --sameas option, not yet used

Browse source
This commit is contained in:
Joey Hess 2019-10-01 12:36:25 -04:00
parent 7b5ce2b330
commit 61b384d2b7
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
6 changed files with 65 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

5
doc/todo/git-lfs_special_remote_simpler_setup.mdwn
View file

@ -14,6 +14,11 @@ two. url=http:// url=ssh:// won't work, only one value will be used.
url1= url2= is annoying for the user, especially if they later want to add
another url with enableremote and have to work out the number.
> If each url is treated as a separate special remote (which makes a lot of sense
> by analogy with how regular git remotes work), then
> [[support_multiple_special_remotes_with_same_uuid]] could be used to
> solve this.
Problem: The user might go in and change the remote's url to point to some
other server with a different git-lfs backend. In fact, they could already
do so! Remembering the urls actually would let the special remote detect

14
doc/todo/support_multiple_special_remotes_with_same_uuid/comment_4_76d747fe5fb8296d8728cc3af7503972._comment Normal file
View file

@ -0,0 +1,14 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2019-10-01T16:26:12Z"
content="""
The RemoteConfig is generated each run from the remote.log, and so the
handling of sameas remotes needs to be done in Logs.Remote.readRemoteLog
not by enableremote.
Logs.Remote.configSet will need some changes because it currently works
on the basis of UUID, and so can't know when it's supposed to change a
sameas remote. It seems it should instead work on the basis of the "name"
field of the RemoteConfig.
"""]]