This commit is contained in:
Joey Hess 2010-11-07 00:26:44 +00:00
parent a3519c365f
commit b1e26b19c6
2 changed files with 20 additions and 1 deletions

View file

@ -0,0 +1,20 @@
It should be possible for clones to learn about how to contact
each other without remotes needing to always be explicitly set
up. Say that `.git-annex/remote.log` is maintained by git-annex
to contain:
UUID hostname URI
The URI comes from configured remotes and maybe from
`file://$(pwd)` for the current repo. This format will merge
without conflicts or data loss.
Then when content is belived to be in a UUID, and no
configured remote has it, the remote.log can be consulted and
URIs that look likely tried. (file:// ones if the hostname
is the same (or maybe always -- a removable drive might tend
to be mounted at the same location on different hosts),
otherwise ssh:// ones.)
Question: When should git-annex update the remote.log?
(Not just on init.) Whenever it reads in a repo's remotes?