@matheusbsbs / matheus-bagliano / commits / 287416dba6
Fork 0

Doc: show example scissors line

The text tries to say the code accepts many variations that look remotely like scissors and perforation marks, but gives too little detail for users to decide what is and what is not taken as a scissors line for themselves. Instead of describing the heuristics more, just spell out what will always be accepted, namely "-- >8 --", as it would not help users to give them more choices and flexibility and be "creative" in their scissors line. Signed-off-by: Evan Gates <evan.gates@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

Evan Gates committed Sep 28, 2020 at 15:51 UTC 287416dba6258ab1819060fb62bb5df5d25aa10e
1 file changed +3 -4
Documentation/git-mailinfo.txt
+3 -4
@@ -72,10 +72,9 @@ conversion, even with this flag.
72 is useful in order to associate commits with mailing list discussions.
73
74 --scissors::
75 - Remove everything in body before a scissors line. A line that
76 - mainly consists of scissors (either ">8" or "8<") and perforation
77 - (dash "-") marks is called a scissors line, and is used to request
78 - the reader to cut the message at that line. If such a line
75 + Remove everything in body before a scissors line (e.g. "-- >8 --").
76 + The line represents scissors and perforation marks, and is used to
77 + request the reader to cut the message at that line. If that line
78 appears in the body of the message before the patch, everything
79 before it (including the scissors line itself) is ignored when
80 this option is used.