From: Roman Gushchin <roman.gushchin@linux.dev>
To: SeongJae Park <sj@kernel.org>
Cc: sashiko@lists.linux.dev, damon@lists.linux.dev
Subject: Re: When Sashiko updates baselines?
Date: Thu, 14 May 2026 22:27:53 +0000 [thread overview]
Message-ID: <7ia4pl2x62za.fsf@castle.c.googlers.com> (raw)
In-Reply-To: <20260514205555.51653-1-sj@kernel.org> (SeongJae Park's message of "Thu, 14 May 2026 13:55:55 -0700")
SeongJae Park <sj@kernel.org> writes:
> Hello,
>
>
> I posted my patch series [1] after rebasing to the latest mm-new
> (0cec77cfd5314c0b3b03530abe1a4b32e991f639). And Sashiko smartly tried to apply
> it on the mm-new, but an older version of the mm-new
> (7505bb13a9bb1f214310915ccc06643119fdafc9), and therefore failed [2].
>
> I could rebase my series on the older version of mm-new and repost, but
> wondering if Sashiko will use the lateset mm-new for the new version and fail
> again. Is there a way to predict what baseline Sashiko will use, or give a
> hint [3]?
Hey SJ!
Sashiko is periodically fetching from remote repositories, but not on
every patch (that would put too much load on kernel.org). There is some
heuristic in place, but it sounds like it's not perfect.
I'll take a look.
Thanks
>
> [1] https://sashiko.dev/#/patchset/20260514140904.119781-1-sj%40kernel.org
> [2] https://sashiko.dev/#/log/baseline/20264/2
> [3] https://lore.kernel.org/sashiko/20260426204746.93567-1-sj@kernel.org/
>
>
> Thanks,
> SJ
prev parent reply other threads:[~2026-05-14 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 20:55 When Sashiko updates baselines? SeongJae Park
2026-05-14 22:27 ` Roman Gushchin [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=7ia4pl2x62za.fsf@castle.c.googlers.com \
--to=roman.gushchin@linux.dev \
--cc=damon@lists.linux.dev \
--cc=sashiko@lists.linux.dev \
--cc=sj@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 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.