1- trailer.separators::
1+ ` trailer.separators` ::
22 This option tells which characters are recognized as trailer
3- separators. By default only ':' is recognized as a trailer
4- separator, except that '=' is always accepted on the command
3+ separators. By default only `:` is recognized as a trailer
4+ separator, except that `=` is always accepted on the command
55 line for compatibility with other git commands.
66+
77The first character given by this option will be the default character
88used when another separator is not specified in the config for this
99trailer.
1010+
11- For example, if the value for this option is " %=$" , then only lines
12- using the format ' <key><sep><value>' with <sep > containing '%' , '='
13- or '$' and then spaces will be considered trailers. And '%' will be
11+ For example, if the value for this option is ` %=$` , then only lines
12+ using the format _ <key><sep><value>_ with _ <sep>_ containing `%` , `=`
13+ or `$` and then spaces will be considered trailers. And `%` will be
1414the default separator used, so by default trailers will appear like:
15- ' <key>% <value>' (one percent sign and one space will appear between
15+ ` <key>% <value>` (one percent sign and one space will appear between
1616the key and the value).
1717
18- trailer.where::
18+ ` trailer.where` ::
1919 This option tells where a new trailer will be added.
2020+
2121This can be `end` , which is the default, `start` , `after` or `before` .
@@ -27,41 +27,41 @@ If it is `start`, then each new trailer will appear at the start,
2727instead of the end, of the existing trailers.
2828+
2929If it is `after` , then each new trailer will appear just after the
30- last trailer with the same <key >.
30+ last trailer with the same _ <key>_ .
3131+
3232If it is `before` , then each new trailer will appear just before the
33- first trailer with the same <key >.
33+ first trailer with the same _ <key>_ .
3434
35- trailer.ifexists::
35+ ` trailer.ifexists` ::
3636 This option makes it possible to choose what action will be
3737 performed when there is already at least one trailer with the
38- same <key > in the input.
38+ same _ <key>_ in the input.
3939+
4040The valid values for this option are: `addIfDifferentNeighbor` (this
4141is the default), `addIfDifferent` , `add` , `replace` or `doNothing` .
4242+
4343With `addIfDifferentNeighbor` , a new trailer will be added only if no
44- trailer with the same (<key >, <value >) pair is above or below the line
44+ trailer with the same (_ <key>_ , _ <value>_ ) pair is above or below the line
4545where the new trailer will be added.
4646+
4747With `addIfDifferent` , a new trailer will be added only if no trailer
48- with the same (<key >, <value >) pair is already in the input.
48+ with the same (_ <key>_ , _ <value>_ ) pair is already in the input.
4949+
5050With `add` , a new trailer will be added, even if some trailers with
51- the same (<key >, <value >) pair are already in the input.
51+ the same (_ <key>_ , _ <value>_ ) pair are already in the input.
5252+
53- With `replace` , an existing trailer with the same <key > will be
53+ With `replace` , an existing trailer with the same _ <key>_ will be
5454deleted and the new trailer will be added. The deleted trailer will be
55- the closest one (with the same <key >) to the place where the new one
55+ the closest one (with the same _ <key>_ ) to the place where the new one
5656will be added.
5757+
5858With `doNothing` , nothing will be done; that is no new trailer will be
59- added if there is already one with the same <key > in the input.
59+ added if there is already one with the same _ <key>_ in the input.
6060
61- trailer.ifmissing::
61+ ` trailer.ifmissing` ::
6262 This option makes it possible to choose what action will be
6363 performed when there is not yet any trailer with the same
64- <key > in the input.
64+ _ <key>_ in the input.
6565+
6666The valid values for this option are: `add` (this is the default) and
6767`doNothing` .
@@ -70,67 +70,68 @@ With `add`, a new trailer will be added.
7070+
7171With `doNothing` , nothing will be done.
7272
73- trailer.<keyAlias >.key::
74- Defines a < keyAlias > for the <key >. The < keyAlias > must be a
75- prefix (case does not matter) of the <key >. For example, in `git
76- config trailer.ack.key "Acked-by"` the " Acked-by" is the <key > and
77- the " ack" is the < keyAlias > . This configuration allows the shorter
73+ ` trailer.<key-alias >.key` ::
74+ Defines a _<key-alias>_ for the _ <key>_ . The _<key-alias>_ must be a
75+ prefix (case does not matter) of the _ <key>_ . For example, in `git
76+ config trailer.ack.key "Acked-by"` the ` Acked-by` is the _ <key>_ and
77+ the ` ack` is the _<key-alias>_ . This configuration allows the shorter
7878 `--trailer "ack:..."` invocation on the command line using the "ack"
79- < keyAlias > instead of the longer `--trailer "Acked-by:..."` .
79+ `<key-alias>` instead of the longer `--trailer "Acked-by:..."` .
8080+
81- At the end of the <key >, a separator can appear and then some
82- space characters. By default the only valid separator is ':' ,
81+ At the end of the _ <key>_ , a separator can appear and then some
82+ space characters. By default the only valid separator is `:` ,
8383but this can be changed using the `trailer.separators` config
8484variable.
8585+
8686If there is a separator in the key, then it overrides the default
8787separator when adding the trailer.
8888
89- trailer.<keyAlias >.where::
90- This option takes the same values as the ' trailer.where'
89+ ` trailer.<key-alias >.where` ::
90+ This option takes the same values as the ` trailer.where`
9191 configuration variable and it overrides what is specified by
92- that option for trailers with the specified < keyAlias > .
92+ that option for trailers with the specified _<key-alias>_ .
9393
94- trailer.<keyAlias >.ifexists::
95- This option takes the same values as the ' trailer.ifexists'
94+ ` trailer.<key-alias >.ifexists` ::
95+ This option takes the same values as the ` trailer.ifexists`
9696 configuration variable and it overrides what is specified by
97- that option for trailers with the specified < keyAlias > .
97+ that option for trailers with the specified _<key-alias>_ .
9898
99- trailer.<keyAlias >.ifmissing::
100- This option takes the same values as the ' trailer.ifmissing'
99+ ` trailer.<key-alias >.ifmissing` ::
100+ This option takes the same values as the ` trailer.ifmissing`
101101 configuration variable and it overrides what is specified by
102- that option for trailers with the specified < keyAlias > .
102+ that option for trailers with the specified _<key-alias>_ .
103103
104- trailer.<keyAlias >.command::
105- Deprecated in favor of ' trailer.<keyAlias >.cmd' .
106- This option behaves in the same way as ' trailer.<keyAlias >.cmd' , except
104+ ` trailer.<key-alias >.command` ::
105+ Deprecated in favor of ` trailer.<key-alias >.cmd` .
106+ This option behaves in the same way as ` trailer.<key-alias >.cmd` , except
107107 that it doesn't pass anything as argument to the specified command.
108- Instead the first occurrence of substring $ARG is replaced by the
109- <value > that would be passed as argument.
108+ Instead the first occurrence of substring ` $ARG` is replaced by the
109+ _ <value>_ that would be passed as argument.
110110+
111- Note that $ARG in the user's command is
112- only replaced once and that the original way of replacing $ARG is not safe.
111+ Note that ` $ARG` in the user's command is
112+ only replaced once and that the original way of replacing ` $ARG` is not safe.
113113+
114- When both ' trailer.<keyAlias >.cmd' and ' trailer.<keyAlias >.command' are given
115- for the same < keyAlias >, ' trailer.<keyAlias >.cmd' is used and
116- ' trailer.<keyAlias >.command' is ignored.
114+ When both ` trailer.<key-alias >.cmd` and ` trailer.<key-alias >.command` are given
115+ for the same _<key-alias>_ , ` trailer.<key-alias >.cmd` is used and
116+ ` trailer.<key-alias >.command` is ignored.
117117
118- trailer.<keyAlias >.cmd::
118+ ` trailer.<key-alias >.cmd` ::
119119 This option can be used to specify a shell command that will be called
120- once to automatically add a trailer with the specified < keyAlias > , and then
121- called each time a ' --trailer <keyAlias >=<value>' argument is specified to
122- modify the <value > of the trailer that this option would produce.
120+ once to automatically add a trailer with the specified _<key-alias>_ , and then
121+ called each time a ` --trailer <key-alias >=<value>` argument is specified to
122+ modify the _ <value>_ of the trailer that this option would produce.
123123+
124124When the specified command is first called to add a trailer
125- with the specified < keyAlias > , the behavior is as if a special
126- ' --trailer <keyAlias >=<value>' argument was added at the beginning
127- of the " git interpret-trailers" command , where <value >
128- is taken to be the standard output of the command with any
129- leading and trailing whitespace trimmed off.
125+ with the specified _<key-alias>_ , the behavior is as if a special
126+ ` --trailer <key-alias >=<value>` argument was added at the beginning
127+ of linkgit: git- interpret-trailers[1] , where _ <value>_ is taken to be the
128+ standard output of the command with any leading and trailing whitespace
129+ trimmed off.
130130+
131- If some ' --trailer <keyAlias >=<value>' arguments are also passed
131+ If some ` --trailer <key-alias >=<value>` arguments are also passed
132132on the command line, the command is called again once for each
133- of these arguments with the same < keyAlias > . And the <value > part
133+ of these arguments with the same _<key-alias>_ . And the _ <value>_ part
134134of these arguments, if any, will be passed to the command as its
135- first argument. This way the command can produce a <value > computed
136- from the <value > passed in the '--trailer <keyAlias>=<value>' argument.
135+ first argument. This way the command can produce a _<value>_ computed
136+ from the _<value>_ passed in the `--trailer <key-alias>=<value>`
137+ argument.
0 commit comments