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

idea

Browse source
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
Download patch file Download diff file Expand all files Collapse all files

1
debian/changelog vendored
View file

@ -4,7 +4,6 @@ git-annex (0.03) UNRELEASED; urgency=low
* Add --verbose * Add --verbose
* Fix SIGINT handling. * Fix SIGINT handling.
* Fix handling of files with unusual characters in their name. * Fix handling of files with unusual characters in their name.
* Support building with Debian stable's ghc.
* Fixed memory leak; git-annex no longer reads the whole file list * Fixed memory leak; git-annex no longer reads the whole file list
from git before starting, and will be much faster with large repos. from git before starting, and will be much faster with large repos.
* Fix crash on unknown symlinks. * Fix crash on unknown symlinks.

20
doc/todo/auto_remotes.mdwn Normal file
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?