aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar lhunath@3b4ff15f4600f3276d1776a490b734fca0f5c245 <lhunath@web>2017-02-22 16:12:10 +0000
committerGravatar admin <admin@branchable.com>2017-02-22 16:12:10 +0000
commit5cb52e7b6171ffc82fd827270fde42e82014dcd5 (patch)
tree46a14c72a92d0b027669a43ca8e43d02e3f351fe /doc
parent6049ce12be169163f401703d60217f81f55eb436 (diff)
Diffstat (limited to 'doc')
-rw-r--r--doc/forum/Upspin.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/forum/Upspin.mdwn b/doc/forum/Upspin.mdwn
new file mode 100644
index 000000000..0ef764130
--- /dev/null
+++ b/doc/forum/Upspin.mdwn
@@ -0,0 +1,5 @@
+As soon as I read about Upspin, I thought about git-annex. Could Upspin's interfaces be beneficial to the project and provide a standardization for naming, permissions and access control?
+
+I realize some of these concepts are not yet part of git-annex, but I thought I'd drop the note and give you the opportunity to evaluate the extent in which Upspin makes sense in the context of git-annex.
+
+https://upspin.io/