summaryrefslogtreecommitdiff
path: root/doc/todo/add_a_git_backend.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/todo/add_a_git_backend.mdwn')
-rw-r--r--doc/todo/add_a_git_backend.mdwn18
1 files changed, 0 insertions, 18 deletions
diff --git a/doc/todo/add_a_git_backend.mdwn b/doc/todo/add_a_git_backend.mdwn
deleted file mode 100644
index 2b224710e..000000000
--- a/doc/todo/add_a_git_backend.mdwn
+++ /dev/null
@@ -1,18 +0,0 @@
-There should be a backend where the file content is stored.. in a git
-repository!
-
-This way, you know your annexed content is safe & versioned, but you only
-have to deal with the pain of git with large files in one place, and can
-use all of git-annex's features everywhere else.
-
-> Speaking as a future user, do very, very much want. -- RichiH
-
->> Might also be interesting to use `bup` in the git backend, to work
->> around git's big file issues there. So git-annex would pull data out
->> of the git backend using bup. --[[Joey]]
-
->>> Very much so. Generally speaking, having one or more versioned storage back-ends with current data in the local annexes sounds incredibly useful. Still being able to get at old data in via the back-end and/or making offline backups of the full history are excellent use cases. -- RichiH
-
-[[done]], the bup special remote type is written! --[[Joey]]
-
-> Yay! -- RichiH