LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Jeremy Kerr <jk@ozlabs.org>, Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linuxppc-dev@lists.ozlabs.org, maddy@linux.ibm.com
Subject: Re: Ozlabs patchwork notification not working anymore
Date: Mon, 25 Aug 2025 11:54:17 +0200	[thread overview]
Message-ID: <7b7cccf2-5899-4334-9aa0-e83f0772d484@csgroup.eu> (raw)
In-Reply-To: <cd2ee23092e3749f707b0f730af741a94f0986f0.camel@ozlabs.org>

Hi Jeremy,

Le 10/08/2025 à 05:12, Jeremy Kerr a écrit :
> Hi Christophe,
> 
> I've (finally!) had some time to take a look at this. Looks like
> timezone behaviour had changed, which affected notification expiry.
> 
> It should be fixed now - I'm seeing test notifications myself. Let
> me know how go.

I still don't receive anything it seems. I have modified the status of 
several patches over the last two weeks and haven't received any 
notification from patchwork.

Christophe

> 
> Cheers,
> 
> 
> Jeremy
> 
> On Tue, 2025-07-29 at 18:32 +1000, Stephen Rothwell wrote:
>> 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 ?
>>
> 



  reply	other threads:[~2025-08-25 10:20 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
2025-08-10  3:12   ` Jeremy Kerr
2025-08-25  9:54     ` Christophe Leroy [this message]
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=7b7cccf2-5899-4334-9aa0-e83f0772d484@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=jk@ozlabs.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=sfr@canb.auug.org.au \
    /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