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

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

From
MBMarc Branchaud <mbranchaud@xiplink.com>
Date
Nov 8, 2012, 16:24 UTC
Message-ID
<509BDCC3.1050107@xiplink.com>
In-Reply-To
<509BA2E7.4080102@alum.mit.edu>
On 12-11-08 07:17 AM, Michael Haggerty wrote:
Show 21 quoted lines
> On 11/08/2012 12:39 PM, Ævar Arnfjörð Bjarmason wrote:
>> [...]
> 
> I'm glad it's getting some use.  Thanks for the feedback.
> 
>> I'll test it out some more, the issues I've had with it so far in
>> migrating from the existing script + some custom hacks we have to it
>> have been:
>>
>>  * Overly verbose default templates, easy to overwrite now. Might send
>>    patches for some of them.
> 
> The templating is currently not super flexible nor very well documented,
> but simple changes should be easy enough.  I mostly carried over the
> text explanations from the old post-receive-email script; it is true
> that they are quite verbose.
> 
>>  * No ability to link to a custom gitweb, probably easy now.
> 
> What do you mean by "a custom gitweb"?  What are the commitmail issues
> involved?

We would also like to have a gitweb link in the summary email, like Ævar describes.

Show 10 quoted lines
>>  * If someone only pushes one commit I'd like to only have one e-mail
>>    with the diff, but if they push multiple commits I'd like to have a
>>    summary e-mail and replies to that which have the patches.
>>
>>    It only seemed to support the latter mode, so you send out two
>>    e-mails for pushing one commit.
> 
> That's correct, and I've also thought about the feature that you
> described.  I think it would be pretty easy to implement; it is only not
> quite obvious to which mailing list(s?) such emails should be sent.
Overall, what should be the approach to the separate mailing lists?

Maybe I don't understand how the script is meant to work. We configured things here with 'mailinglist' and 'commitlist' set to different lists. Now if someone wants to get both the summary and per-commit emails, they need to be on both lists. If I understand correctly, if all 4 mailing lists are distinct, someone who wants all the emails needs to be on all of them. This seems a little awkward.

I'd like there to be one list that always gets everything, and the other lists should get subsets of the everything list.

		M.
Previous: Michael HaggertyNext: Ævar Arnfjörð Bjarmason
Message 21 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.