summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U <Richard@web>2011-03-28 15:20:59 +0000
committerGravatar admin <admin@branchable.com>2011-03-28 15:20:59 +0000
commit73b4fe5d61e492fe537f04d3971f25970b7ebf3f (patch)
tree947d9442725e69709e99f1c943af1a856d06ba14
parent3b3a60dfab38676142c45a5de5eec7849fb49380 (diff)
-rw-r--r--doc/forum/wishlist:_git_backend_for_git-annex.mdwn7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/forum/wishlist:_git_backend_for_git-annex.mdwn b/doc/forum/wishlist:_git_backend_for_git-annex.mdwn
new file mode 100644
index 000000000..63ae83097
--- /dev/null
+++ b/doc/forum/wishlist:_git_backend_for_git-annex.mdwn
@@ -0,0 +1,7 @@
+Preamble: Obviously, the core feature of git-annex is the ability to keep a subset of files in a local repo. The main trade-off is that you don't get version tracking.
+
+Use case: On my laptop, I might not have enough disk space to store everything. Not so for my main box nor my backup server. And I would _really_ like to have proper version tracking for many of my files. Thus...
+
+Wish: ...why not use git as a version backend? That way, I could just push all my stuff to the central instance(s) and have the best of both worlds. Depending on what backend is used in the local repos, it might make sense to define a list of supported client backends with pre-computed keys.
+
+-- RichiH