From: Junio C Hamano <gitster@pobox•com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>
Cc: Jeremy Morton <admin@game-point•net>, git@vger•kernel.org
Subject: Re: Running interpret-trailers automatically on each commit?
Date: Mon, 31 Aug 2015 10:48:24 -0700 [thread overview]
Message-ID: <xmqqio7vwdqv.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <vpqmvx7ho5r.fsf@anie.imag.fr> (Matthieu Moy's message of "Mon, 31 Aug 2015 10:12:32 +0200")
Matthieu Moy <Matthieu.Moy@grenoble-inp•fr> writes:
> Jeremy Morton <admin@game-point•net> writes:
>
>> 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).
>
> Please, don't top-post on this list.
>
> Actually, it seems strange to me to activate it on a per-user basis.
> Whether you add a trailer is usually a per-project policy. If you add a
> branch trailer in each of your repository, it seems likely that some
> projects you contribute to will be bothered by this.
>
> That said, I agree it would be nice to allow a configuration-based
> mechanism in addition to the current hook-based one we currently have.
> But no one stepped in to implement it until now ...
Certanly. A new experimental feature is shipped in 2.2 timeframe,
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. It is not "no one stepped in to
implement until now", but more like "no one designed what to
implement".
And we still do not have a concrete design on what to implement on
the table. "At various points in the codebase, interpret-trailers
is invoked with some magic parameters, depending on settings of
unspecified set of configuration variables" is not a design.
next prev parent reply other threads:[~2015-08-31 17:48 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
2015-08-31 8:12 ` Matthieu Moy
2015-08-31 17:48 ` Junio C Hamano [this message]
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=xmqqio7vwdqv.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=Matthieu.Moy@grenoble-inp$(echo .)fr \
--cc=admin@game-point$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
/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