Skip to contentSkip to conversation

Enable notifications for linux-mtd

DISCUSSION Boris Brezillon 3 participants 6 messages Nov 7, 2017 – Nov 9, 2017 Memory technology devices (MTD)

lore
Share & tools
lore
#0 lore raw

Hi Jeremy,

Is there a way to send notifications to the submitter/author when the status of a linux-mtd patch is changed? I didn't find such an option in the config/profile menu, but I already received such notifications when contributing to other projects.

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.

Thanks,

Boris

#1 lore raw

Hi Boris,

Quoted 2 lines

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?

Quoted 2 lines

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?

Cheers,

Jeremy

#2 lore raw

Hi Jeremy,

Quoted 7 lines · On Wed, 8 Nov 2017 09:29:35 +0800 Jeremy Kerr <[email protected]> wrote:

Hi Boris,

Quoted 2 lines

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?

Quoted 6 lines
Quoted 3 lines

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

#3 lore raw
In reply to Jeremy Kerr
Quoted 7 lines · Jeremy Kerr

Hi Boris,

Quoted 2 lines

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?

What does "notification to submitter/author" mean? Only to the person who sent the patch? Or to everyone CC'd (including the mailing list)? If it's not the latter, then I hope no maintainer starts relying on that. It really obscures the process if authors are getting private notifications, and nobody ever responds publicly to say things have been applied.

Quoted 5 lines
Quoted 2 lines

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?

In general, mailing lists get a lot of inapplicable junk. Cross-posts, at least (e.g., device tree source changes, documentation, and driver patches in a single series -- we might only care about the latter 2). Does that mean we notify submitters when things move to "Not Applicable"? What about "Archived"? There's still non-archived stuff on the tracker that's >3 years old. I guess spamming people isn't the end of the world...

Brian

#4 lore raw
Quoted 9 lines · On Wed, 8 Nov 2017 22:10:16 -0800 Brian Norris <[email protected]>…
Quoted 7 lines · Jeremy Kerr

Hi Boris,

Quoted 2 lines

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?

Quoted 6 lines

What does "notification to submitter/author" mean? Only to the person who sent the patch? Or to everyone CC'd (including the mailing list)? If it's not the latter, then I hope no maintainer starts relying on that. It really obscures the process if authors are getting private notifications, and nobody ever responds publicly to say things have been applied.

That's true. Jeremy, are notifications sent to all people in Cc of a patch/patch-series, or is it just sent to the submitter and author of the patch?

Quoted 16 lines
Quoted 6 lines
Quoted 3 lines

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?

In general, mailing lists get a lot of inapplicable junk. Cross-posts, at least (e.g., device tree source changes, documentation, and driver patches in a single series -- we might only care about the latter 2). Does that mean we notify submitters when things move to "Not Applicable"? What about "Archived"? There's still non-archived stuff on the tracker that's >3 years old. I guess spamming people isn't the end of the world...

Brian

#5 lore raw

Hi Boris,

Quoted 10 lines
Quoted 6 lines

What does "notification to submitter/author" mean? Only to the person who sent the patch? Or to everyone CC'd (including the mailing list)? If it's not the latter, then I hope no maintainer starts relying on that. It really obscures the process if authors are getting private notifications, and nobody ever responds publicly to say things have been applied.

That's true. Jeremy, are notifications sent to all people in Cc of a patch/patch-series, or is it just sent to the submitter and author of the patch?

Just the submitter - ie., the person who sent it to the list.

Cheers,

Jeremy