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

Re: [RFC] Add a new email notification script to "contrib"

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 16, 2012, 19:21 UTC
Message-ID
<7v629n1pho.fsf@alter.siamese.dyndns.org>
In-Reply-To
<500465E3.8040501@alum.mit.edu>
Michael Haggerty <mhagger@alum.mit.edu> writes:
Show 37 quoted lines
> On 07/16/2012 07:47 PM, Junio C Hamano wrote:
>> Michael Haggerty <mhagger@alum.mit.edu> writes:
>>
>>> It's already supported:
>>>
>>>      git config hooks.announcelist \
>>>          "nosy@example.com, overwhelmed@example.com, phb@example.com"
>>>      git config hooks.refchangelist \
>>>          "nosy@example.com, overwhelmed@example.com"
>>>      git config hooks.commitlist "nosy@example.com"
>>
>> Sad.  Is the "post-recieve email" squatting on the _whole_ hooks.*
>> namespace, not postreceiveemailhook.* or something more reasonably
>> limited?
>
> Yes.  I didn't like this either, but I copied this aspect of the old
> script in the interest of compatibility.
>
> If we want to change this, now would be a good time, before the new
> script starts using more of the hooks namespace.  One could choose a
> new namespace and deprecate the old one, optionally in multiple steps:
>
> 1. Only read new options from new namespace; read old options from new
> namespace or (if the new names are not set) falling back to the old
> namespace.
>
> 2. Deprecate the old namespace, emitting warnings if the old names are
> still set but continuing to use them.
>
> 3. Stop supporting the old namespace, but emit warnings if the old
> names are still set.
>
> 4. Stop looking in the old namespace altogether.
>
> Though, given that hook scripts have to be enabled/upgraded
> per-repository, usually on a central server, probably doing only steps
> 2 and 4 would be enough.

It would be sufficient to add a README that gives a one-time migration instruction (bonus point if a script to automate the process is given) in the commit that replaces the old script with the new one.

Previous: Michael HaggertyNext: Matthieu Moy
Message 12 of 26 in “[RFC] Add a new email notification script to "contrib"”
  1. mhagger@alum.mit.eduJul 14, 2012
  2. Stefan NäweJul 14, 2012
  3. Michael HaggertyJul 15, 2012
  4. Junio C HamanoJul 15, 2012
  5. Michael HaggertyJul 15, 2012
  6. Marc BranchaudJul 16, 2012
  7. Michael HaggertyJul 16, 2012
  8. Matthieu MoyJul 16, 2012
  9. Michael HaggertyJul 16, 2012
  10. Junio C HamanoJul 16, 2012
  11. Michael HaggertyJul 16, 2012
  12. Junio C HamanoJul 16, 2012
  13. Matthieu MoyJul 18, 2012
  14. Michael HaggertyJul 20, 2012
  15. Ævar Arnfjörð BjarmasonNov 7, 2012
  16. Michael HaggertyNov 8, 2012
  17. Ævar Arnfjörð BjarmasonNov 8, 2012
  18. Michael HaggertyNov 8, 2012
  19. Ævar Arnfjörð BjarmasonNov 8, 2012
  20. Michael HaggertyNov 22, 2012
  21. Marc BranchaudNov 8, 2012
  22. Ævar Arnfjörð BjarmasonNov 8, 2012
  23. Marc BranchaudNov 8, 2012
  24. Marc BranchaudNov 8, 2012
  25. Michael HaggertyNov 22, 2012
  26. Stefan NaeweJul 14, 2012

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.