From: Christian Couder <christian.couder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Mar 2014, #06; Tue, 25)
Date: Wed, 26 Mar 2014 10:03:50 +0100 [thread overview]
Message-ID: <CAP8UFD3YuGuekwrzrx7Qr_saDyLSo7Chvggb7ygTuie9w0T93g@mail.gmail.com> (raw)
In-Reply-To: <xmqqlhvykp62.fsf@gitster.dls.corp.google.com>
HI,
On Tue, Mar 25, 2014 at 9:18 PM, Junio C Hamano <gitster@pobox.com> wrote:
>
> * cc/interpret-trailers (2014-03-07) 11 commits
> - Documentation: add documentation for 'git interpret-trailers'
> - trailer: add tests for commands in config file
> - trailer: execute command from 'trailer.<name>.command'
> - trailer: add tests for "git interpret-trailers"
> - trailer: add interpret-trailers command
> - trailer: put all the processing together and print
> - trailer: parse trailers from stdin
> - trailer: process command line trailer arguments
> - trailer: read and process config information
> - trailer: process trailers from stdin and arguments
> - trailers: add data structures and basic functions
>
> A new filter to programatically edit the tail end of the commit log
> messages.
>
> Will merge to 'next'.
I have a new version of this series, but I am not very happy with it.
Especially, I am not very happy about not using strcasecmp() and
instead lowercasing some parameters read from the config file.
That's because it adds some lines and one more patch as I feel that I
have to refactor lowercasing functions.
I will send this new series soon anyway and we can choose if we want
these lowercasing changes or not.
Thanks,
Christian.
prev parent reply other threads:[~2014-03-26 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 20:18 What's cooking in git.git (Mar 2014, #06; Tue, 25) Junio C Hamano
2014-03-26 9:03 ` Christian Couder [this message]
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=CAP8UFD3YuGuekwrzrx7Qr_saDyLSo7Chvggb7ygTuie9w0T93g@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).