Skip to content

Commit 45087db

Browse files
LukeShuchriscool
authored andcommitted
git-fast-export.txt: clarify why 'verbatim' may not be a good idea
Signed-off-by: Luke Shumaker <[email protected]> Signed-off-by: Christian Couder <[email protected]>
1 parent 947bc26 commit 45087db

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

Documentation/git-fast-export.adoc

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,15 +29,19 @@ OPTIONS
2929

3030
--signed-tags=(verbatim|warn-verbatim|warn-strip|strip|abort)::
3131
Specify how to handle signed tags. Since any transformation
32-
after the export can change the tag names (which can also happen
33-
when excluding revisions) the signatures will not match.
32+
after the export (or during the export, such as excluding
33+
revisions) can change the hashes being signed, the signatures
34+
may become invalid.
3435
+
3536
When asking to 'abort' (which is the default), this program will die
3637
when encountering a signed tag. With 'strip', the tags will silently
3738
be made unsigned, with 'warn-strip' they will be made unsigned but a
3839
warning will be displayed, with 'verbatim', they will be silently
3940
exported and with 'warn-verbatim' (or 'warn', a deprecated synonym),
40-
they will be exported, but you will see a warning.
41+
they will be exported, but you will see a warning. 'verbatim' and
42+
'warn-verbatim' should only be used if you know that no
43+
transformation affecting tags will be performed, or if you do not
44+
care that the resulting tag will have an invalid signature.
4145

4246
--tag-of-filtered-object=(abort|drop|rewrite)::
4347
Specify how to handle tags whose tagged object is filtered out.

0 commit comments

Comments
 (0)