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

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

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Jul 15, 2012, 22:45 UTC
Message-ID
<500347F9.3040005@alum.mit.edu>
In-Reply-To
<7v1ukd5wis.fsf@alter.siamese.dyndns.org>
On 07/15/2012 09:11 AM, Junio C Hamano wrote:
Show 11 quoted lines
> mhagger@alum.mit.edu writes:
>> Add a new Python script, contrib/hooks/post-receive-multimail.py, that
>> can be used to send notification emails describing pushes into a git
>> repository.  This script is derived from
>> contrib/hooks/post-receive-mail, but has many differences, including:
>
> The new script (I didn't read it at all) may be useful to some
> people, but I'm fairly negative on adding 47 different "I know there
> is something in contrib/, I looked at it, but I didn't bother
> updating it to fill my needs and wrote a new one instead" at this
> point to my tree.
I understand your concern.
Show 11 quoted lines
> It is a different matter if the patch was to replace the existing
> one, saying "the users of the old script can use this one, which is
> backward compatible with respect to the external interface such as
> command line, or configuration variables used".  Instead of a total
> backward compatibility, "here is a script to migrate the existing
> set of configuration variables so that users of the old script can
> run it once, and start using this new one" is also perfectly fine.
>
> Such an enhancement, especially if the rewritten result is cleaner
> and easier to enhance going forward than the original, would be very
> much appreciated.

I didn't originally put the new script forward as a replacement for the old one mainly because it seems that Python is relatively unwelcome in the git project. But if the use of Python doesn't disqualify it, then yes, I think the new script (with a little more work) will be a worthy replacement for the old shell script.

The new script is already mostly compatible with the old one:
* It accepts the same command-line arguments and uses most of the same 
configuration variables.
* It is possible to configure the new script to send only the refchange 
summary emails and skip sending the emails for individual commits, 
though I would want to put some work into supporting this mode better.
* I tested the earliest versions of the new script by verifying that its 
output was identical to that of the shell script.  (Of course the output 
is no longer identical; I claim that it is now better :-) .)

So I think it would be quite possible to touch up the new script to make it a drop-in replacement for the old one, and I am willing to do so. If I understand correctly that there is a non-negligible chance of this happening, then I will continue working towards that goal.

Michael
Previous: Junio C HamanoNext: Marc Branchaud
Message 5 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.