[PATCH] Documentation/fast-export: Document --import-marks and --export-marks options
- From
- Pieter de Bie <pdebie@ai.rug.nl>
- Date
- Jun 7, 2008, 13:25 UTC
- Message-ID
- <1212845104-79789-1-git-send-email-pdebie@ai.rug.nl>
- In-Reply-To
- <1212663163-43064-1-git-send-email-pdebie@ai.rug.nl>
This adds a description for git-fast-export's --import-marks and --export-marks options to its man page. ---
I forgot to add the options to the man page. Perhaps this should be squashed on top of the other patch?
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 332346c..277a547 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 --------
-- 1.5.6.rc0.165.ge08d6b.dirty