From b1e26b19c6055b8c635a158068a2ad0188f17d17 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sun, 7 Nov 2010 00:26:44 +0000 Subject: idea --- debian/changelog | 1 - doc/todo/auto_remotes.mdwn | 20 ++++++++++++++++++++ 2 files changed, 20 insertions(+), 1 deletion(-) create mode 100644 doc/todo/auto_remotes.mdwn diff --git a/debian/changelog b/debian/changelog index ae68f657b..1d3c6427f 100644 --- a/debian/changelog +++ b/debian/changelog @@ -4,7 +4,6 @@ git-annex (0.03) UNRELEASED; urgency=low * Add --verbose * Fix SIGINT handling. * 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 from git before starting, and will be much faster with large repos. * Fix crash on unknown symlinks. diff --git a/doc/todo/auto_remotes.mdwn b/doc/todo/auto_remotes.mdwn new file mode 100644 index 000000000..4976a2a77 --- /dev/null +++ b/doc/todo/auto_remotes.mdwn @@ -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? -- cgit v1.2.3