diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U <Richard@web> | 2011-03-14 17:06:30 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2011-03-14 17:06:30 +0000 |
| commit | a4993f9321702d75d93c76227a8b8ee2fd863fb1 (patch) | |
| tree | 4e13d06d3a8edadf012fd6c02c2139e4147270d9 | |
| parent | 61396e34b5c9cb8b94940e9e83baf4e1a9466205 (diff) | |
| -rw-r--r-- | doc/todo/add_a_git_backend.mdwn | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/todo/add_a_git_backend.mdwn b/doc/todo/add_a_git_backend.mdwn index 25e780269..34322d981 100644 --- a/doc/todo/add_a_git_backend.mdwn +++ b/doc/todo/add_a_git_backend.mdwn @@ -10,3 +10,5 @@ use all of git-annex's features everywhere else. >> 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 |