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

git-multimail resurected!

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
May 29, 2015, 13:10 UTC
Message-ID
<vpqr3pz5y35.fsf@anie.imag.fr>
Hi,

This is my pleasure to write this first message as git-multimail [1] co-maintainer. git-multimail allows sending automatic notification emails after a "git push". It was initially written by Michael Haggerty as a greatly improved replacement for post-receive-email. Michael has been a great developer and reviewer for a while (and thanks again for that!), but lost personal interest in the tool a while ago, and asked me if I wanted to take over the maintainership when we met at Git Merge. We currently co-maintain the tool.

I finally got some time to go through the pending pull-requests. I could close 19 PR, and we still have 10 pending. For more details about what happened recently, see the GitHub pulse [2]. Pleasant to look at :-).

Other than fixes, we have the following new features in master:
* When a single commit is pushed, omit the reference changed email.
  Set multimailhook.combineWhenSingleCommit to false to disable this
  new feature.
* In gitolite environments, the pusher's email address can be used as
  the From address by creating a specially formatted comment block in
  gitolite.conf (see multimailhook.from in README).
* Support for SMTP authentication/SSL was added, see smtpUser,
  smtpPass, smtpEncryption in README.
* A new option scanCommitForCc was added to allow git-multimail to
  search the commit message for 'Cc: ...' lines, and add the
  corresponding emails in Cc.
* If $USER is not set, use the variable $USERNAME. This is needed on
  Windows platform to recognize the pusher.
* The emailPrefix variable can now be set to an empty string to remove
  the prefix.
* A short tutorial was added in doc/gitolite.rst to set up
  git-multimail with gitolite.
* The post-receive file was renamed to post-receive.example. It has
  always been an example (the standard way to call git-multimail is to
  call git_multimail.py), but it was unclear to many users.
Next to review&merge on my TODO-list:
* Add an option to show a graph of commits in addition to the log in the
  summary message [3].
* Allow filtering on refs, so that mails can be sent only when pushing
  to a subset of branches/tags/... [4].

I plan to tag a 1.1 release in June. Don't hesitate to join the fun and help by reviewing pull-requests or submitting new ones!

[1] https://github.com/git-multimail/git-multimail [2] https://github.com/git-multimail/git-multimail/pulse/monthly [3] https://github.com/git-multimail/git-multimail/pull/90 [4] https://github.com/git-multimail/git-multimail/pull/52

Cheers,
-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Message 1 of 1 in “git-multimail resurected!”
  1. Matthieu MoyMay 29, 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.