Sorry for reappearing in this thread after such a long absence. I
wanted to see what is coming up (I think this interpret-trailers command
will be handy!) so I read this documentation patch carefully, and added
some questions and suggestions below.
On 04/06/2014 07:02 PM, Christian Couder wrote:
> Signed-off-by: Christian Couder <chrisc...@tuxfamily.org>
> Signed-off-by: Junio C Hamano <gits...@pobox.com>
> Documentation/git-interpret-trailers.txt | 123
> 1 file changed, 123 insertions(+)
> create mode 100644 Documentation/git-interpret-trailers.txt
> diff --git a/Documentation/git-interpret-trailers.txt
> new file mode 100644
> index 0000000..75ae386
> --- /dev/null
> +++ b/Documentation/git-interpret-trailers.txt
> @@ -0,0 +1,123 @@
> +git-interpret-trailers - help add stuctured information into commit messages
> +'git interpret-trailers' [--trim-empty] [(<token>[(=|:)<value>])...]
> +Help add RFC 822-like headers, called 'trailers', at the end of the
> +otherwise free-form part of a commit message.
> +This command is a filter. It reads the standard input for a commit
> +message and applies the `token` arguments, if any, to this
> +message. The resulting message is emited on the standard output.
> +Some configuration variables control the way the `token` arguments are
> +applied to the message and the way any existing trailer in the message
> +is changed. They also make it possible to automatically add some
> +By default, a 'token=value' or 'token:value' argument will be added
> +only if no trailer with the same (token, value) pair is already in the
> +message. The 'token' and 'value' parts will be trimmed to remove
> +starting and trailing whitespace, and the resulting trimmed 'token'
> +and 'value' will appear in the message like this:
> +token: value
> +By default, if there are already trailers with the same 'token', the
> +new trailer will appear just after the last trailer with the same
> +'token'. Otherwise it will appear at the end of the message.
How are existing trailers recognized in the input commit message? Do
trailers have to be configured to be recognized? Or are all lines
matching a specific pattern considered trailers? If so, it might be
helpful to include a regexp here that describes the trailer "syntax".
What about blank lines? I see that you try to add a blank line before
new trailers. But what about on input? Do the trailer lines have to be
separated from the free-form comment by a blank line to be recognized?
What if there are blank lines between trailer lines, or after them? Is
it allowed to have non-trailer lines between or after trailer lines?
> +Note that 'trailers' do not follow and are not intended to follow many
> +rules that are in RFC 822. For example they do not follow the line
> +breaking rules, the encoding rules and probably many other rules.
> + If the 'value' part of any trailer contains only whitespace,
> + the whole trailer will be removed from the resulting message.
Does this apply to existing trailers, new trailers, or both? If it
applies to existing trailers, then it seems a bit dangerous, in the
sense that the command might end up changing trailers that are unrelated
to the one that the command is trying to add.
> +CONFIGURATION VARIABLES
> + This 'key' will be used instead of 'token' in the
> + trailer. After some alphanumeric characters, it can contain
Trailer keys can also contain '-', right?
> + some non alphanumeric characters like ':', '=' or '#' that will
> + be used instead of ':' to separate the token from the value in
> + the trailer, though the default ':' is more standard.
Above it looks like the default separator is not ':' but rather ': '
(with a space). Is the space always added regardless of the value of
this configuration variable, or should the configuration value include
the trailing space if it is desired? Is there any way to get a trailer
that doesn't include a space, like
? (Changing this to "foo= bar" would look pretty ugly.)
If a commit message containing trailer lines with separators other than
':' is input to the program, will it recognize them as trailer lines?
Do such trailer lines have to have the same separator as the one listed
in this configuration setting to be recognized?
I suppose that there is some compelling reason to allow non-colon
separators here. If not, it seems like it adds a lot of complexity and
should maybe be omitted, or limited to only a few specific separators.
> + This can be either `after`, which is the default, or
> + `before`. If it is `before`, then a trailer with the specified
> + token, will appear before, instead of after, other trailers
> + with the same token, or otherwise at the beginning, instead of
> + at the end, of all the trailers.
Brainstorming: some other options that might make sense here someday:
`end`: add new trailer after all existing trailers (even those with
different keys). This would allow trailers to be kept in chronological
`beginning`: add new trailer before the first existing trailer (allows
reverse chronological order).
`sorted`: add new trailer among the existing trailers with the same key
so as to keep their values in lexicographic order.
> + This option makes it possible to choose what action will be
> + performed when there is already at least one trailer with the
> + same token in the message.
> +The valid values for this option are: `addIfDifferent` (this is the
> +default), `addIfDifferentNeighbor`, `add`, `overwrite` or `doNothing`.
Are these option values case sensitive? If so, it might be a little bit
confusing because the same camel-case is often used in documentation for
configuration *keys*, which are not case sensitive , and users might
have gotten used to thinking of strings that look like this to be
> +With `addIfDifferent`, a new trailer will be added only if no trailer
> +with the same (token, value) pair is already in the message.
> +With `addIfDifferentNeighbor`, a new trailer will be added only if no
> +trailer with the same (token, value) pair is above or below the line
> +where the new trailer will be added.
> +With `add`, a new trailer will be added, even if some trailers with
> +the same (token, value) pair are already in the message.
> +With `overwrite`, the new trailer will overwrite an existing trailer
> +with the same token.
What if there are multiple existing trailers with the same token? Are
they all overwritten?
> +With `doNothing`, nothing will be done, that is no new trailer will be
> +added if there is already one with the same token in the message.
> + This option makes it possible to choose what action will be
> + performed when there is not yet any trailer with the same
> + token in the message.
> +The valid values for this option are: `add` (this is the default) and
> +With `add`, a new trailer will be added.
> +With `doNothing`, nothing will be done.
> + This option can be used to specify a shell command that will
> + be used to automatically add or modify a trailer with the
> + specified 'token'.
> +When this option is specified, it is like if a special 'token=value'
> +argument is added at the end of the command line, where 'value' will
> +be given by the standard output of the specified command.
Maybe reword to
When this option is specified, the behavior is as if a special
'token=value' argument were added at the end of the command line,
where 'value' is taken to be the standard output of the specified
And if it is the case, maybe add "with leading and trailing whitespace
trimmed off" at the end of the sentence.
> +If the command contains the `$ARG` string, this string will be
> +replaced with the 'value' part of an existing trailer with the same
> +token, if any, before the command is launched.
What if the key appears multiple times in existing trailers?
> +SEE ALSO
> +Part of the linkgit:git suite
Doesn't this command have to be added to command-list.txt?
 Anti-nitpick declaration: yes, I know that the middle part of
configuration keys is case-sensitive.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html