diff options
| author | Jed Brown <jed@jedbrown.org> | 2014-08-08 08:45:25 -0500 |
|---|---|---|
| committer | Jed Brown <jed@jedbrown.org> | 2014-08-08 08:45:50 -0500 |
| commit | 85da17389833c44f0bf69fa64faa4c58c32c16c7 (patch) | |
| tree | bb78a3c37a97b3527eaa3bcde14413b0d35587a3 | |
| parent | 829b91d794a0809991987d2d95c7bab60b97acaf (diff) | |
| download | git-fat-85da17389833c44f0bf69fa64faa4c58c32c16c7.tar.gz | |
README: add nuance to description of git clone --depth
Closes #47
Suggested-by: Aleksander Nitecki
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -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 |