From: Junio C Hamano <gitster@pobox•com>
To: Stefan Beller <sbeller@google•com>
Cc: Christian Couder <christian.couder@gmail•com>, git <git@vger•kernel.org>
Subject: Re: [PATCH] Introduce a hook to run after formatting patches
Date: Thu, 20 Nov 2014 15:33:26 -0800 [thread overview]
Message-ID: <xmqqioi91m7t.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20141120232628.GA30554@google.com> (Stefan Beller's message of "Thu, 20 Nov 2014 15:26:28 -0800")
Stefan Beller <sbeller@google•com> writes:
> So I have read the man page on the trailers and it seems like the solution
> to my problem in removing parts from the commit message.
> However I did not find out, if it can be run automatically, whenever
> calling format-patch
>
> Maybe all that is missing here is an option
>
> git config format.enable_trailers
> ?
The idea has been to first give a standalone text transmonger as a
filter for let people to try out, so that we know what kind of
changes are useful (e.g. "insert s-o-b at the very end") and make
sure the configuration language to specify the changes is easy and
expressive enough, which is more or less what we have in 'master'.
Once we gain experience (and that may result in updates to what is
in 'master'), in the second phase, we would figure out what code
paths can make use of this text transmonger (e.g. your configuration
variable "format.trailers" to affect the format-patch code path) and
integrate it more tightly to the codebase.
We are not there yet.
next prev parent reply other threads:[~2014-11-20 23:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-15 0:47 [PATCH] Introduce a hook to run after formatting patches Stefan Beller
2014-11-15 10:44 ` Philip Oakley
2014-11-16 18:40 ` Junio C Hamano
2014-11-17 19:01 ` Stefan Beller
2014-11-17 19:06 ` Junio C Hamano
2014-11-17 19:20 ` Junio C Hamano
2014-11-18 6:40 ` Christian Couder
2014-11-20 23:26 ` Stefan Beller
2014-11-20 23:33 ` Junio C Hamano [this message]
2014-11-21 4:31 ` Christian Couder
2014-11-18 2:30 ` Stefan Beller
2014-11-18 17:02 ` Junio C Hamano
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=xmqqioi91m7t.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=christian.couder@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=sbeller@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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