git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v14 00/11] Add interpret-trailers builtin

From
Christian Couder <chriscool@tuxfamily.org>
Date
Sep 15, 2014, 05:31 UTC
Message-ID
<20140915052330.26573.34823.chriscool@tuxfamily.org>
This patch series implements a new command:
        git interpret-trailers

and an infrastructure to process trailers that can be reused, for example in "commit.c".

1) Rationale

This command should help with RFC 822 style headers, called "trailers", that are found at the end of commit messages.

(Note that these headers 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.)

For a long time, these trailers have become a de facto standard way to add helpful information into commit messages.

Until now git commit has only supported the well known "Signed-off-by: " trailer, that is used by many projects like the Linux kernel and Git.

It is better to keep builtin/commit.c uncontaminated by any more hard-wired logic, like what we have for the signed-off-by line. Any new things can and should be doable in hooks, and this filter would help writing these hooks.

And that is why the design goal of the filter is to make it at least as powerful as the built-in logic we have for signed-off-by lines; that would allow us to later eject the hard-wired logic for signed-off-by line from the main codepath, if/when we wanted to.

Alternatively, we could build a library-ish API around this filter code and replace the hard-wired logic for signed-off-by line with a call into that API, if/when we wanted to, but that requires (in addition to the "at least as powerful as the built-in logic") that the implementation of this stand-alone filter can be cleanly made into a reusable library, so that is a bit higher bar to cross than "everything can be doable with hooks" alternative.

2) Current state
Currently the usage string of this command is:
git interpret-trailers [--trim-empty] [(--trailer <token>[(=|:)<value>])...] [<file>...]
The following features are implemented:
        - the result is printed on stdout
        - the --trailer arguments are interpreted
        - messages read from <file>... or stdin are interpreted
        - the "trailer.separators" option in the config is interpreted
        - the "trailer.where" option is interpreted
        - the "trailer.ifexists" option is interpreted
        - the "trailer.ifmissing" option is interpreted
        - the "trailer.<token>.key" options are interpreted
        - the "trailer.<token>.where" options are interpreted
        - the "trailer.<token>.ifexist" options are interpreted
        - the "trailer.<token>.ifmissing" options are interpreted
        - the "trailer.<token>.command" config works
        - $ARG can be used in commands
        - messages can contain a patch
        - lines in messages starting with a comment char are ignored
        - there are 49 tests
        - there is some documentation
        - there are examples in the documentation
3) Changes since version 13, thanks to Marc and Junio
* improved documentation (patch 11/11)
* rework the way trailer.<token>.command are handled, so
  that it is simpler to understand and closer to what is
  described in the documentation (patches 9/11, 10/11
  and 11/11) 
Christian Couder (11):
  trailer: add data structures and basic functions
  trailer: process trailers from input message and arguments
  trailer: read and process config information
  trailer: process command line trailer arguments
  trailer: parse trailers from file or stdin
  trailer: put all the processing together and print
  trailer: add interpret-trailers command
  trailer: add tests for "git interpret-trailers"
  trailer: execute command from 'trailer.<name>.command'
  trailer: add tests for commands in config file
  Documentation: add documentation for 'git interpret-trailers'
 .gitignore                               |   1 +
 Documentation/git-interpret-trailers.txt | 313 ++++++++++++
 Makefile                                 |   2 +
 builtin.h                                |   1 +
 builtin/interpret-trailers.c             |  44 ++
 command-list.txt                         |   1 +
 git.c                                    |   1 +
 t/t7513-interpret-trailers.sh            | 851 +++++++++++++++++++++++++++++++
 trailer.c                                | 847 ++++++++++++++++++++++++++++++
 trailer.h                                |   6 +
 10 files changed, 2067 insertions(+)
 create mode 100644 Documentation/git-interpret-trailers.txt
 create mode 100644 builtin/interpret-trailers.c
 create mode 100755 t/t7513-interpret-trailers.sh
 create mode 100644 trailer.c
 create mode 100644 trailer.h
-- 
2.0.3.960.g41c6e4c
Next: Christian Couder
Message 1 of 16 in “Add interpret-trailers builtin”
  1. 00/11 Add interpret-trailers builtinChristian Couder, Sep 15, 2014
  2. 01/11 trailer: add data structures and basic functionsChristian Couder, Sep 15, 2014
  3. Junio C HamanoSep 15, 2014
  4. Christian CouderSep 16, 2014
  5. Jeff KingSep 17, 2014
  6. Christian CouderSep 17, 2014
  7. 02/11 trailer: process trailers from input message and argumentsChristian Couder, Sep 15, 2014
  8. 03/11 trailer: read and process config informationChristian Couder, Sep 15, 2014
  9. 04/11 trailer: process command line trailer argumentsChristian Couder, Sep 15, 2014
  10. 05/11 trailer: parse trailers from file or stdinChristian Couder, Sep 15, 2014
  11. 06/11 trailer: put all the processing together and printChristian Couder, Sep 15, 2014
  12. 07/11 trailer: add interpret-trailers commandChristian Couder, Sep 15, 2014
  13. 08/11 trailer: add tests for "git interpret-trailers"Christian Couder, Sep 15, 2014
  14. 09/11 trailer: execute command from 'trailer.<name>.command'Christian Couder, Sep 15, 2014
  15. 10/11 trailer: add tests for commands in config fileChristian Couder, Sep 15, 2014
  16. 11/11 Documentation: add documentation for 'git interpret-trailers'Christian Couder, Sep 15, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.