From: Jeremy Morton <admin@game-point.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Running interpret-trailers automatically on each commit?
Date: Fri, 28 Aug 2015 18:07:12 +0100 [thread overview]
Message-ID: <55E09540.60805@game-point.net> (raw)
In-Reply-To: <xmqqk2sf2vic.fsf@gitster.mtv.corp.google.com>
Yeah but it's kind of useless to me having it on each commit on a
per-repo basis (and even then, only with hooks).
--
Best regards,
Jeremy Morton (Jez)
On 28/08/2015 18:06, Junio C Hamano wrote:
> Jeremy Morton<admin@game-point.net> writes:
>
>> I see that interpret-trailers has been added by default in git
>> 2.5.0. However the documentation isn't that great and I can't tell
>> whether it gets run automatically when I do a "git commit". My guess
>> is that it doesn't - that you have to set up a hook to get it to run
>> each commit.
>
> All correct, except that it happend in 2.2 timeframe.
>
> A new experimental feature is shipped, so that people can gain
> experience with it and come up with the best practice in their
> hooks, and then laster we may fold the best practice into somewhere
> deeper in the system.
>
> We are still in the early "ship an experimental feature to let
> people play with it" stage.
>
> Thanks.
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-08-28 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 15:22 Running interpret-trailers automatically on each commit? Jeremy Morton
2015-08-28 17:06 ` Junio C Hamano
2015-08-28 17:07 ` Jeremy Morton [this message]
2015-08-31 8:12 ` Matthieu Moy
2015-08-31 17:48 ` Junio C Hamano
2015-08-31 17:48 ` 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=55E09540.60805@game-point.net \
--to=admin@game-point.net \
--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 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.