From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Johan Herland <johan@herland.net>,
Josh Triplett <josh@joshtriplett.org>,
Thomas Rast <tr@thomasrast.ch>,
Michael Haggerty <mhagger@alum.mit.edu>,
Dan Carpenter <dan.carpenter@oracle.com>,
Greg Kroah-Hartman <greg@kroah.com>, Jeff King <peff@peff.net>,
Jakub Narebski <jnareb@gmail.com>,
Eric Sunshine <sunshine@sunshineco.com>,
Ramsay Jones <ramsay@ramsay1.demon.co.uk>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: [PATCH v13 00/11] Add interpret-trailers builtin
Date: Sat, 16 Aug 2014 18:06:10 +0200 [thread overview]
Message-ID: <20140816153440.18221.29179.chriscool@tuxfamily.org> (raw)
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 (new)
- the "trailer.where" option is interpreted (new)
- the "trailer.ifexists" option is interpreted (new)
- the "trailer.ifmissing" option is interpreted (new)
- 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 12, thanks to Jakub, Michael, Johan and Junio:
* "end" and "start" values for "trailer.<token>.where" have been
implemented
* "end" has been made the default value for "where", but this default
value can be changed using the new "trailer.where" config
variable
* "addIfDifferentNeighbor" is now the default value for "ifexists",
but this default can be changed using the new "trailer.ifexists"
config variable
* the new "trailer.ifmissing" can be used to change the default value
for "ifmissing" (which is "add")
* by default the only separator is ':', this can be changed by using
the new "trailer.separators" config variable
* only the configured separators (or just ':' by default) are used for
both input parsing and output printing; the only exception is that
'=' is always accepted as separator when parsing
"--trailer '<token><sep><value>'" command line arguments, for
compatibility with other git commands
* 14 tests have been added
Only patches 7/11, 9/11 and 10/11 have not been changed since v12.
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 | 308 +++++++++++
Makefile | 2 +
builtin.h | 1 +
builtin/interpret-trailers.c | 44 ++
command-list.txt | 1 +
git.c | 1 +
t/t7513-interpret-trailers.sh | 850 +++++++++++++++++++++++++++++++
trailer.c | 830 ++++++++++++++++++++++++++++++
trailer.h | 6 +
10 files changed, 2044 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.1.674.ga7f57b7
next reply other threads:[~2014-08-16 16:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 16:06 Christian Couder [this message]
2014-08-16 16:06 ` [PATCH v13 01/11] trailer: add data structures and basic functions Christian Couder
2014-08-16 16:06 ` [PATCH v13 02/11] trailer: process trailers from input message and arguments Christian Couder
2014-08-16 16:06 ` [PATCH v13 03/11] trailer: read and process config information Christian Couder
2014-08-16 16:06 ` [PATCH v13 04/11] trailer: process command line trailer arguments Christian Couder
2014-08-16 16:06 ` [PATCH v13 05/11] trailer: parse trailers from file or stdin Christian Couder
2014-08-16 16:06 ` [PATCH v13 06/11] trailer: put all the processing together and print Christian Couder
2014-08-16 16:06 ` [PATCH v13 07/11] trailer: add interpret-trailers command Christian Couder
2014-08-16 16:06 ` [PATCH v13 08/11] trailer: add tests for "git interpret-trailers" Christian Couder
2014-08-16 16:06 ` [PATCH v13 09/11] trailer: execute command from 'trailer.<name>.command' Christian Couder
2014-08-16 16:06 ` [PATCH v13 10/11] trailer: add tests for commands in config file Christian Couder
2014-08-16 16:06 ` [PATCH v13 11/11] Documentation: add documentation for 'git interpret-trailers' Christian Couder
2014-08-20 22:05 ` Marc Branchaud
2014-08-21 3:39 ` Christian Couder
2014-08-21 14:16 ` Marc Branchaud
2014-08-16 22:25 ` [PATCH v13 00/11] Add interpret-trailers builtin Christian Couder
2014-09-03 21:30 ` Junio C Hamano
2014-09-15 6:04 ` Christian Couder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140816153440.18221.29179.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=dan.carpenter@oracle.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=greg@kroah.com \
--cc=jnareb@gmail.com \
--cc=johan@herland.net \
--cc=josh@joshtriplett.org \
--cc=jrnieder@gmail.com \
--cc=mhagger@alum.mit.edu \
--cc=peff@peff.net \
--cc=ramsay@ramsay1.demon.co.uk \
--cc=sunshine@sunshineco.com \
--cc=tr@thomasrast.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.