diff options
author | Pieter de Bie <pdebie@ai.rug.nl> | 2008-06-11 13:17:04 +0200 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2008-06-19 15:52:53 -0700 |
commit | df6a7ff7ac55d320afa1b8a59393122d6ca0f6c4 (patch) | |
tree | d970fad945945bf0966fec8c3504f8e777a36354 /Documentation | |
parent | e449f105805ffa49ccf7cf080db897ecf65a1a0f (diff) | |
download | git-df6a7ff7ac55d320afa1b8a59393122d6ca0f6c4.tar.gz git-df6a7ff7ac55d320afa1b8a59393122d6ca0f6c4.tar.xz |
builtin-fast-export: Add importing and exporting of revision marks
This adds the --import-marks and --export-marks to fast-export. These import
and export the marks used to for all revisions exported in a similar fashion
to what fast-import does. The format is the same as fast-import, so you can
create a bidirectional importer / exporter by using the same marks file on
both sides.
Signed-off-by: Pieter de Bie <pdebie@ai.rug.nl>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/git-fast-export.txt | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/Documentation/git-fast-export.txt b/Documentation/git-fast-export.txt index 332346cc5..277a547a0 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 -------- |