aboutsummaryrefslogtreecommitdiff
path: root/doc/todo/untracked_remotes.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2013-08-07 12:26:10 -0400
committerGravatar Joey Hess <joey@kitenet.net>2013-08-07 12:26:10 -0400
commit6220c3e8dae21da3b262598fda0c4ecb2c42d233 (patch)
tree9d8ef0be68f79dcc5997040762b73289a13884c1 /doc/todo/untracked_remotes.mdwn
parentf5ce5498b90fc0f64ca81e9ded8a57f545392a7d (diff)
add
Diffstat (limited to 'doc/todo/untracked_remotes.mdwn')
-rw-r--r--doc/todo/untracked_remotes.mdwn9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/todo/untracked_remotes.mdwn b/doc/todo/untracked_remotes.mdwn
new file mode 100644
index 000000000..883b5acff
--- /dev/null
+++ b/doc/todo/untracked_remotes.mdwn
@@ -0,0 +1,9 @@
+Seems that a fairly common desire in some use cases is to be able to make a
+clone of a repository and be able to get files, without updating the
+location tracking information. (And without even recording a uuid in the
+remote.log.) Use cases include wanting to have temporary
+clones without cluttering history, and centralized development where the
+developers don't care to know about one-another's systems.
+
+It seems that such an untracked repository would need to automatically
+consider itself untrusted. Is that enough to avoid losing data?