From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: tools@linux.kernel.org
Subject: Re: pw-bot on kernel Patchwork misses pulls with different proto
Date: Thu, 22 Jan 2026 13:28:10 -0500 [thread overview]
Message-ID: <20260122-fancy-hidden-parrot-ce21ec@lemur> (raw)
In-Reply-To: <f8463626-68c6-4b3e-ac0c-5a01db8e7755@kernel.org>
On Thu, Jan 22, 2026 at 06:31:53PM +0100, Krzysztof Kozlowski wrote:
> Hey,
>
> After merging pull requests to soc.git, I expected pw-bot to react -
> change status in Patchwork and send thank you letter, but probably my
> insteadOf rules confused the pwbot:
I committed a fix for this that only matches by path and tag, which should
still be unique enough to avoid clashes:
https://git.kernel.org/pub/scm/linux/kernel/git/mricon/korg-helpers.git/commit/?id=44169ff49ab3707fb1c84f2ed2ab340c47ff698e
-K
prev parent reply other threads:[~2026-01-22 18:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 17:31 pw-bot on kernel Patchwork misses pulls with different proto Krzysztof Kozlowski
2026-01-22 18:28 ` Konstantin Ryabitsev [this message]
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=20260122-fancy-hidden-parrot-ce21ec@lemur \
--to=konstantin@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=tools@linux.kernel.org \
/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