From 6c54e21c54be19750f93193ba1c8950c98ceebf5 Mon Sep 17 00:00:00 2001 From: "http://christian.amsuess.com/chrysn" Date: Sat, 21 Sep 2013 15:01:42 +0000 Subject: fix wording (sparse checkout -> shallow clone), more details, formatting --- doc/users/chrysn.mdwn | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) (limited to 'doc') diff --git a/doc/users/chrysn.mdwn b/doc/users/chrysn.mdwn index f5c07b88b..ba4261567 100644 --- a/doc/users/chrysn.mdwn +++ b/doc/users/chrysn.mdwn @@ -1,5 +1,11 @@ * **name**: chrysn * **website**: -* **uses git-annex for**: managing the family's photos (and possibly videos and music in the future) -* **likes git-annex because**: it adds a layer of commit semantics over a regular file system without keeping everything in duplicate locally -* **would like git-annex to**: not be required any more as git itself learns to use cow filesystems to avoid abundant disk usage and gets better with sparser checkouts (git-annex might then still be a simpler tool that watches over what can be safely dropped for a sparser checkout) +* **uses git-annex for** managing the family's photos (and possibly videos and music in the future). +* **likes git-annex because** it adds a layer of commit semantics over a regular file system without keeping everything in duplicate locally. +* **would like git-annex not to** be required any more at all when + * git itself learns to use cow filesystems to avoid abundant disk usage, and + * git gets better with shallow clones. + + git-annex might then still be a simpler tool that watches over what can be safely dropped from a particular shallow clone + + (the issues with shallow clones seem to relate primarily to shallow history; i haven't read anything about what would happen if all commits were checked out, but not all trees and blobs) -- cgit v1.2.3