git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Running interpret-trailers automatically on each commit?

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 31, 2015, 17:48 UTC
Message-ID
<xmqqio7vwdqv.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<vpqmvx7ho5r.fsf@anie.imag.fr>
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
Show 15 quoted lines
> 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.

Previous: Matthieu MoyNext: Junio C Hamano
Message 5 of 6 in “Running interpret-trailers automatically on each commit?”
  1. Jeremy MortonAug 28, 2015
  2. Junio C HamanoAug 28, 2015
  3. Jeremy MortonAug 28, 2015
  4. Matthieu MoyAug 31, 2015
  5. Junio C HamanoAug 31, 2015
  6. Junio C HamanoAug 31, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.