From: Stephen Rothwell <sfr@canb.auug.org.au>
To: LEROY Christophe <christophe.leroy2@cs-soprasteria.com>
Cc: <linuxppc-dev@lists.ozlabs.org>, <maddy@linux.ibm.com>,
Jeremy Kerr <jk@ozlabs.org>
Subject: Re: Ozlabs patchwork notification not working anymore
Date: Tue, 29 Jul 2025 18:32:22 +1000 [thread overview]
Message-ID: <20250729183222.15adbb95@canb.auug.org.au> (raw)
In-Reply-To: <8f6e5825-9468-4499-9bbd-4588a1eccc94@cs-soprasteria.com>
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]
Hi Christophe,
On Tue, 29 Jul 2025 07:41:40 +0000 LEROY Christophe <christophe.leroy2@cs-soprasteria.com> wrote:
>
> If I remember correctly you maintain the Ozlabs patchwork aren't you ?
Actually Jeremy Kerr (cc'd) actually manages patchwork on
patchwork.ozlabs.org (I just admin the server it runs on).
> For more than one year now, patchwork for linuxppc-dev hasn't sent
> notifications about patches status changes. Last notification I received
> was 11 June 2024.
>
> Is there a reason for that change ? I recently got questions from people
> asking me why they didn't get notified when I started looking at their
> patches.
>
> Is it possible to restore previous behaviour ?
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-07-29 8:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 7:41 Ozlabs patchwork notification not working anymore LEROY Christophe
2025-07-29 8:32 ` Stephen Rothwell [this message]
2025-08-10 3:12 ` Jeremy Kerr
2025-08-25 9:54 ` Christophe Leroy
2025-08-26 2:24 ` Jeremy Kerr
2025-08-26 10:09 ` Christophe Leroy
2026-07-27 9:27 ` Ozlabs patchwork very very slow very often Christophe Leroy (CS GROUP)
2026-07-27 9:42 ` 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=20250729183222.15adbb95@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=christophe.leroy2@cs-soprasteria.com \
--cc=jk@ozlabs.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.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).