git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed

From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: git <git@vger.kernel.org>
Cc: Michael Haggerty <mhagger@alum.mit.edu>
Subject: git-multimail resurected!
Date: Fri, 29 May 2015 15:10:06 +0200	[thread overview]
Message-ID: <vpqr3pz5y35.fsf@anie.imag.fr> (raw)

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/

                 reply	other threads:[~2015-05-29 13:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vpqr3pz5y35.fsf@anie.imag.fr \
    --to=matthieu.moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=mhagger@alum.mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).