All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Jeremy Kerr <jk@ozlabs.org>
Cc: Brian Norris <computersforpeace@gmail.com>,
	Richard Weinberger <richard@nod.at>, Marek Vasut <marex@denx.de>,
	Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
	David Woodhouse <dwmw2@infradead.org>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Enable notifications for linux-mtd
Date: Wed, 8 Nov 2017 09:22:33 +0100	[thread overview]
Message-ID: <20171108092233.3812521a@bbrezillon> (raw)
In-Reply-To: <46cc2db3-fa2d-61ab-5e78-c88d9f371584@ozlabs.org>

Hi Jeremy,

On Wed, 8 Nov 2017 09:29:35 +0800
Jeremy Kerr <jk@ozlabs.org> wrote:

> Hi Boris,
> 
> > Is there a way to send notifications to the submitter/author when the
> > status of a linux-mtd patch is changed?  
> 
> Absolutely - that's just something I can turn on in your project's
> config. I assume your co-maintainers are OK with this?

I now for sure that Richard is fine with that. Cyrille, Marek, Brian,
any problem with enabling notifications for linux-mtd?

> 
> > Not sure we'll need a notification for any kind of change, but having
> > one when the patch is marked as Accepted would be good.  
> 
> Currently, the notifications are for all state changes (there's no
> config to do it selectively). Will this be a problem?

No, that's fine. It's just that notifying when the state moves to
'Changes Requested' is a bit redundant, because the review would attest
that. Same goes for 'Superseded', the user is already aware that his
new version supersedes the old one. Anyway, it's really not a big deal,
and I'd be happy with notifications for all state changes.

Thanks,

Boris

  reply	other threads:[~2017-11-08  8:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07  8:26 Enable notifications for linux-mtd Boris Brezillon
2017-11-08  1:29 ` Jeremy Kerr
2017-11-08  8:22   ` Boris Brezillon [this message]
2017-11-09  6:10   ` Brian Norris
2017-11-09  8:37     ` Boris Brezillon
2017-11-09  9:17       ` Jeremy Kerr

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=20171108092233.3812521a@bbrezillon \
    --to=boris.brezillon@free-electrons.com \
    --cc=computersforpeace@gmail.com \
    --cc=cyrille.pitchen@wedev4u.fr \
    --cc=dwmw2@infradead.org \
    --cc=jk@ozlabs.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marex@denx.de \
    --cc=richard@nod.at \
    /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.