summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2008-06-22 14:32:58 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2008-06-22 14:32:58 -0700
commitdd503ed4d121e24888f3b20c0f353857b164b6a1 (patch)
tree21e940bfbe9b33af7ace374213a1180422a63148 /Documentation
parentMerge branch 'mo/status-untracked' (diff)
parentbuiltin-fast-export: Add importing and exporting of revision marks (diff)
downloadtgif-dd503ed4d121e24888f3b20c0f353857b164b6a1.tar.xz
Merge branch 'pb/fast-export'
* pb/fast-export: builtin-fast-export: Add importing and exporting of revision marks
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/git-fast-export.txt20
1 files changed, 20 insertions, 0 deletions
diff --git a/Documentation/git-fast-export.txt b/Documentation/git-fast-export.txt
index 332346cc5d..277a547a02 100644
--- a/Documentation/git-fast-export.txt
+++ b/Documentation/git-fast-export.txt
@@ -36,6 +36,26 @@ when encountering a signed tag. With 'strip', the tags will be made
unsigned, with 'verbatim', they will be silently exported
and with 'warn', they will be exported, but you will see a warning.
+--export-marks=<file>::
+ Dumps the internal marks table to <file> when complete.
+ Marks are written one per line as `:markid SHA-1`. Only marks
+ for revisions are dumped; marks for blobs are ignored.
+ Backends can use this file to validate imports after they
+ have been completed, or to save the marks table across
+ incremental runs. As <file> is only opened and truncated
+ at completion, the same path can also be safely given to
+ \--import-marks.
+
+--import-marks=<file>::
+ Before processing any input, load the marks specified in
+ <file>. The input file must exist, must be readable, and
+ must use the same format as produced by \--export-marks.
++
+Any commits that have already been marked will not be exported again.
+If the backend uses a similar \--import-marks file, this allows for
+incremental bidirectional exporting of the repository by keeping the
+marks the same across runs.
+
EXAMPLES
--------