From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: sashiko@lists.linux.dev
Subject: prerequisite-message-id handling
Date: Wed, 12 Aug 2026 12:14:01 +0200 [thread overview]
Message-ID: <anxHaUk_i0_ZPMr8@lpieralisi> (raw)
Hi,
I have noticed that sashiko failed to review:
https://sashiko.dev/#/message/20260812-gicv5-7-2-fixes-v1-0-3743e82c69a4%40kernel.org
because it does not apply. I added, through b4, base-commit and
prerequisite-message-id to the cover letter but AFAICS from the log only
the former was taken into account while building the baseline, that
also matches the guidelines:
https://github.com/sashiko-dev/sashiko/blob/main/MAINTAINERS_GUIDE.md
Just asking if, for future postings, there is a way to handle patches
dependencies and feed that info to sashiko.
Thanks,
Lorenzo
next reply other threads:[~2026-08-12 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 10:14 Lorenzo Pieralisi [this message]
2026-08-17 20:25 ` prerequisite-message-id handling Roman Gushchin
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=anxHaUk_i0_ZPMr8@lpieralisi \
--to=lpieralisi@kernel.org \
--cc=sashiko@lists.linux.dev \
/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.