From 79559f27be7e2963213d840a857dee92c579843f Mon Sep 17 00:00:00 2001 From: Geoffrey Irving Date: Mon, 27 Jul 2009 22:20:22 -0400 Subject: git fast-export: add --no-data option When using git fast-export and git fast-import to rewrite the history of a repository with large binary files, almost all of the time is spent dealing with blobs. This is extremely inefficient if all we want to do is rewrite the commits and tree structure. --no-data skips the output of blobs and writes SHA-1s instead of marks, which provides a massive speedup. Signed-off-by: Geoffrey Irving Signed-off-by: Junio C Hamano --- Documentation/git-fast-export.txt | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'Documentation/git-fast-export.txt') diff --git a/Documentation/git-fast-export.txt b/Documentation/git-fast-export.txt index af2328d401..75b06f33e7 100644 --- a/Documentation/git-fast-export.txt +++ b/Documentation/git-fast-export.txt @@ -82,6 +82,14 @@ marks the same across runs. allow that. So fake a tagger to be able to fast-import the output. +--no-data:: + Skip output of blob objects and instead refer to blobs via + their original SHA-1 hash. This is useful when rewriting the + directory structure or history of a repository without + touching the contents of individual files. Note that the + resulting stream can only be used by a repository which + already contains the necessary objects. + [git-rev-list-args...]:: A list of arguments, acceptable to 'git-rev-parse' and 'git-rev-list', that specifies the specific objects and references -- cgit v1.2.3