git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Haggerty <mhagger@alum.mit.edu>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
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, 22 Nov 2012 08:32:49 +0100	[thread overview]
Message-ID: <50ADD521.8020909@alum.mit.edu> (raw)
In-Reply-To: <CACBZZX4gzgTZCk78PYpYHnKdwQ0vScoLz02tuAuUQRXVVXSLVg@mail.gmail.com>

On 11/08/2012 04:38 PM, Ævar Arnfjörð Bjarmason wrote:
> On Thu, Nov 8, 2012 at 1:17 PM, Michael Haggerty <mhagger@alum.mit.edu> wrote:
>> On 11/08/2012 12:39 PM, Ævar Arnfjörð Bjarmason wrote:
>>> 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 just sending the individual patch e-mails to all people who
> subscribe to paths that got changed in that patch that match their
> watchlist makes sense.

I forgot to mention, but Environment.get_revision_recipients() has all
the information needed to implement such a policy.  You could override
this method in your own Environment class to get the behavior that you want.

> That script *also* supports sending the whole batch of patches pushed
> in that push to someone watching any file that got modified in one of
> the patches, in case you also want to get other stuff pushed in pushes
> for files you're interested in.

This is not yet possible without more intrusive code changes.

Michael

-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/

  reply	other threads:[~2012-11-22 23:04 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
2012-11-08 12:17         ` Michael Haggerty
2012-11-08 15:38           ` Ævar Arnfjörð Bjarmason
2012-11-22  7:32             ` Michael Haggerty [this message]
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=50ADD521.8020909@alum.mit.edu \
    --to=mhagger@alum.mit.edu \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=andyparkins@gmail.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mbranchaud@xiplink.com \
    --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 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 NNTP newsgroup(s).