From 85da17389833c44f0bf69fa64faa4c58c32c16c7 Mon Sep 17 00:00:00 2001 From: Jed Brown Date: Fri, 8 Aug 2014 08:45:25 -0500 Subject: README: add nuance to description of git clone --depth Closes #47 Suggested-by: Aleksander Nitecki --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'README.md') diff --git a/README.md b/README.md index 3889ad2..9526da9 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ Even if the instantaneous working tree stays manageable, preserving repository i Some people recommend checking binaries into different repositories or even not versioning them at all, but these are not satisfying solutions for most workflows. ## Features of `git-fat` -* clones of the source repository are small and fast because no binaries are transferred, yet fully functional (unlike `git clone --depth`) +* clones of the source repository are small and fast because no binaries are transferred, yet fully functional with complete metadata and incremental retrieval (`git clone --depth` has limited granularity and couples metadata to content) * `git-fat` supports the same workflow for large binaries and traditionally versioned files, but internally manages the "fat" files separately * `git-bisect` works properly even when versions of the binary files change over time * selective control of which large files to pull into the local store -- cgit v1.2.1