[prev in list] [next in list] [prev in thread] [next in thread] 

List:       git
Subject:    Re: Running interpret-trailers automatically on each commit?
From:       Junio C Hamano <gitster () pobox ! com>
Date:       2015-08-31 17:48:35
Message-ID: xmqqh9nfwdqk.fsf () gitster ! mtv ! corp ! google ! com
[Download RAW message or body]

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 ...

Certainly.  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.
--
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
[prev in list] [next in list] [prev in thread] [next in thread]