All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: git@vger.kernel.org, "Andy Parkins" <andyparkins@gmail.com>,
	"Sitaram Chamarty" <sitaramc@gmail.com>,
	"Stefan Näwe" <stefan.naewe@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>,
	"Marc Branchaud" <mbranchaud@xiplink.com>,
	"Matthieu Moy" <Matthieu.Moy@grenoble-inp.fr>
Subject: Re: [RFC] Add a new email notification script to "contrib"
Date: Thu, 8 Nov 2012 12:39:34 +0100	[thread overview]
Message-ID: <CACBZZX5FihEMSyrws-D7GyWvxtpMCPwvaiM18ZqOBaoBcvEjDA@mail.gmail.com> (raw)
In-Reply-To: <509B7E6B.1030407@alum.mit.edu>

On Thu, Nov 8, 2012 at 10:42 AM, Michael Haggerty <mhagger@alum.mit.edu> wrote:
> On 11/07/2012 10:47 PM, Ævar Arnfjörð Bjarmason wrote:
>> I'm curious as to whether you got around to this? I'd be interested in
>> updates on this script.
>
> Thanks for asking.  I have made many of the changes that were requested
> and/or I had planned:

I was playing around with it for some work repos last night.

> * Tentatively renamed the system to git-multimail
>
> * Store the configuration in namespace "multimailhook.*" instead of
> "hooks.*".

Great, I had made this change locally myself, makes it much easier to
keep the configuration separate, and I think doing and having a
migration script is better than using the original config variables.

> * Reinstated (optional) support for including shortlogs since the last
> tag in announce emails.
>
> * Script to migrate post-receive-email configuration to the equivalent
> git-multimail config.
>
> * Better documentation (including of the migration process).
>
> * Made it easier to use Python code to customize the script's behavior
> (by allowing it to be imported as a Python module), plus a demo script
> showing this usage.

That's very nice, I was monkeypatching the script to overwrite some
templates. This makes that easy.

> * Some primitive testing tools to generate a test git repository and
> generate many kinds of notification emails (though the emails still have
> to be checked manually for correctness).
>
> Nevertheless I think that the script is quite usable as it is and it
> would be great if other people could try it out, give feedback, and even
> submit patches.

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.
 * No ability to link to a custom gitweb, probably easy now.
 * 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.
 * Ability to limit the number of lines, but not line length, that's
   handy for some template repositories. Should be easy to add
 * I wanted a hook to override the options passed to sendmail in some
   cases, looks easier now with the modular design.

But in addition to that we have our own custom E-Mail notification
scripts for:

 * People can subscribe to changes to certain files. I.e. if you
   modify very_important.c we'll send an E-Mail to a more widely seen
   review list.

 * Invididuals can also edit a config file to watch individual files /
   glob patterns of files, e.g. src/main.c or src/crypto*

I think a good way to support that would be to have either a path to a
config file with those watch specs, or a command so you could run "git
show ..." on some repo users can push to.

But overall it's very nice. I'll make some time to test it in my
organization (with lots of commits and people reading commit e-mails).

  reply	other threads:[~2012-11-08 11:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-14  6:59 [RFC] Add a new email notification script to "contrib" mhagger
2012-07-14  9:46 ` Stefan Näwe
     [not found]   ` <CALUzUxoi-X2nTTFF7utJz2DOTDE8-s7QOgR=HmQAkOVkGY17BA@mail.gmail.com>
2012-07-14 12:03     ` Stefan Naewe
2012-07-15  4:38   ` Michael Haggerty
2012-07-15  7:11 ` Junio C Hamano
2012-07-15 22:45   ` Michael Haggerty
2012-07-16 15:57 ` Marc Branchaud
2012-07-16 16:38   ` Michael Haggerty
2012-07-16 16:16 ` Matthieu Moy
2012-07-16 16:48   ` Michael Haggerty
2012-07-16 17:47     ` Junio C Hamano
2012-07-16 19:05       ` Michael Haggerty
2012-07-16 19:21         ` Junio C Hamano
2012-07-18  7:52 ` Matthieu Moy
2012-07-20 10:01 ` Michael Haggerty
2012-11-07 21:47   ` Ævar Arnfjörð Bjarmason
2012-11-08  9:42     ` Michael Haggerty
2012-11-08 11:39       ` Ævar Arnfjörð Bjarmason [this message]
2012-11-08 12:17         ` Michael Haggerty
2012-11-08 15:38           ` Ævar Arnfjörð Bjarmason
2012-11-22  7:32             ` Michael Haggerty
2012-11-08 16:24           ` Marc Branchaud
2012-11-08 16:37             ` Ævar Arnfjörð Bjarmason
2012-11-08 16:46               ` Marc Branchaud
2012-11-08 16:03       ` Marc Branchaud
2012-11-22  7:27         ` Michael Haggerty

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

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

  git send-email \
    --in-reply-to=CACBZZX5FihEMSyrws-D7GyWvxtpMCPwvaiM18ZqOBaoBcvEjDA@mail.gmail.com \
    --to=avarab@gmail.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=andyparkins@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mbranchaud@xiplink.com \
    --cc=mhagger@alum.mit.edu \
    --cc=sitaramc@gmail.com \
    --cc=stefan.naewe@gmail.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.