1GIT-FAST-EXPORT(1) Git Manual GIT-FAST-EXPORT(1)
2
6 git-fast-export - Git data exporter
7
9 git fast-export [options] | git fast-import
10
12 This program dumps the given revisions in a form suitable to be piped
13 into git fast-import.
14 You can use it as a human-readable bundle replacement (see git-
16 bundle(1)), or as a kind of an interactive git filter-branch.
17
19 --progress=<n>
20 Insert progress statements every <n> objects, to be shown by git
21 fast-import during import.
22 --signed-tags=(verbatim|warn|strip|abort)
24 Specify how to handle signed tags. Since any transformation after
25 the export can change the tag names (which can also happen when
26 excluding revisions) the signatures will not match.
27 When asking to abort (which is the default), this program will die
29 when encountering a signed tag. With strip, the tags will be made
30 unsigned, with verbatim, they will be silently exported and with
31 warn, they will be exported, but you will see a warning.
32 --tag-of-filtered-object=(abort|drop|rewrite)
34 Specify how to handle tags whose tagged object is filtered out.
35 Since revisions and files to export can be limited by path, tagged
36 objects may be filtered completely.
37 When asking to abort (which is the default), this program will die
39 when encountering such a tag. With drop it will omit such tags from
40 the output. With rewrite, if the tagged object is a commit, it will
41 rewrite the tag to tag an ancestor commit (via parent rewriting;
42 see git-rev-list(1))
43 -M, -C
45 Perform move and/or copy detection, as described in the git-diff(1)
46 manual page, and use it to generate rename and copy commands in the
47 output dump.
48 Note that earlier versions of this command did not complain and
50 produced incorrect results if you gave these options.
51 --export-marks=<file>
53 Dumps the internal marks table to <file> when complete. Marks are
54 written one per line as :markid SHA-1. Only marks for revisions are
55 dumped; marks for blobs are ignored. Backends can use this file to
56 validate imports after they have been completed, or to save the
57 marks table across incremental runs. As <file> is only opened and
58 truncated at completion, the same path can also be safely given to
59 --import-marks.
60 --import-marks=<file>
62 Before processing any input, load the marks specified in <file>.
63 The input file must exist, must be readable, and must use the same
64 format as produced by --export-marks.
65 Any commits that have already been marked will not be exported
67 again. If the backend uses a similar --import-marks file, this
68 allows for incremental bidirectional exporting of the repository by
69 keeping the marks the same across runs.
70 --fake-missing-tagger
72 Some old repositories have tags without a tagger. The fast-import
73 protocol was pretty strict about that, and did not allow that. So
74 fake a tagger to be able to fast-import the output.
75 --no-data
77 Skip output of blob objects and instead refer to blobs via their
78 original SHA-1 hash. This is useful when rewriting the directory
79 structure or history of a repository without touching the contents
80 of individual files. Note that the resulting stream can only be
81 used by a repository which already contains the necessary objects.
82 [git-rev-list-args...]
84 A list of arguments, acceptable to git rev-parse and git rev-list,
85 that specifies the specific objects and references to export. For
86 example, master\~10..master causes the current master reference to
87 be exported along with all objects added since its 10th ancestor
88 commit.
89
91 $ git fast-export --all | (cd /empty/repository && git fast-import)
92 This will export the whole repository and import it into the existing
95 empty repository. Except for reencoding commits that are not in UTF-8,
96 it would be a one-to-one mirror.
97 $ git fast-export master~5..master |
99 sed "s|refs/heads/master|refs/heads/other|" |
100 git fast-import
101 This makes a new branch called other from master~5..master (i.e. if
104 master has linear history, it will take the last 5 commits).
105 Note that this assumes that none of the blobs and commit messages
107 referenced by that revision range contains the string
108 refs/heads/master.
109
111 Since git fast-import cannot tag trees, you will not be able to export
112 the linux-2.6.git repository completely, as it contains a tag
113 referencing a tree instead of a commit.
114
116 Written by Johannes E. Schindelin <johannes.schindelin@gmx.de[1]>.
117
119 Documentation by Johannes E. Schindelin
120 <johannes.schindelin@gmx.de[1]>.
121
123 Part of the git(1) suite
124
126 1. johannes.schindelin@gmx.de
127 mailto:johannes.schindelin@gmx.de
128Git 1.7.1 08/16/2017 GIT-FAST-EXPORT(1)