From abffea5fcb412ed0161805a0284038bab30dae38 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 21 Mar 2018 09:19:06 -0400 Subject: [PATCH] update --- doc/todo/adb_special_remote.mdwn | 5 +++++ doc/todo/import_tree.mdwn | 10 ++++++++++ 2 files changed, 15 insertions(+) diff --git a/doc/todo/adb_special_remote.mdwn b/doc/todo/adb_special_remote.mdwn index baf9899084..6c72f2a6c1 100644 --- a/doc/todo/adb_special_remote.mdwn +++ b/doc/todo/adb_special_remote.mdwn @@ -14,3 +14,8 @@ repository. And, [[export preferred content]] would be a useful feature for excluding some files from a tree exported to android. + +---- + +initremote will need to store the uuid of the remote in it, to avoid +operating on the wrong device. diff --git a/doc/todo/import_tree.mdwn b/doc/todo/import_tree.mdwn index ee8cc8081b..91aa630bee 100644 --- a/doc/todo/import_tree.mdwn +++ b/doc/todo/import_tree.mdwn @@ -16,6 +16,8 @@ The remote interface needs one new method, to list the changed/new and deleted files. It will be up to remotes to implement that if they can support importing. +---- + One way for a remote to do it, assuming it has mtimes, is to export files to the remote with their mtime set to the date of the treeish being exported (when the treeish is a commit, which has dates, and not @@ -29,4 +31,12 @@ but keep a list somewhere (eg a file on the remote) of the timestamps of each exported file, and then it can later look for files with newer timestamps. +---- + +If multiple repos can access the remote at the same time, then there's a +potential problem when one is exporting a new tree, and the other one is +importing from the remote. + +---- + See also, [[adb_special_remote]]