aboutsummaryrefslogtreecommitdiff
path: root/doc/future_proofing.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-03-05 15:58:57 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-03-05 15:58:57 -0400
commit598027d82489aded053154f7d8f7b5dcf4d79ebb (patch)
treef010eb86476b3504aedca3e1d95666c2d304551e /doc/future_proofing.mdwn
parent6c1607ce66fb456880495d9026fa368ad48eda3e (diff)
update
Diffstat (limited to 'doc/future_proofing.mdwn')
-rw-r--r--doc/future_proofing.mdwn3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/future_proofing.mdwn b/doc/future_proofing.mdwn
index 4d4939b5a..d9a36ff73 100644
--- a/doc/future_proofing.mdwn
+++ b/doc/future_proofing.mdwn
@@ -11,6 +11,9 @@ problem:
files from the repository; they are there on disk in the usual way,
with just some symlinks pointing at the annexed file contents.
Neither git-annex nor git is needed to get at the file contents.
+
+ (Also, git-annex provides an "uninit" command that moves everything out
+ of the annex, if you should ever want to stop using it.)
* What file formats are used? Will they still be readable? To deal with
this, it's best to stick to plain text files, and the most common