On Fri, Aug 14, 2026 at 12:18:50PM +0300, Mike Rapoport wrote: > On Fri, Aug 14, 2026 at 10:01:19AM +0100, Lorenzo Stoakes (ARM) wrote: > > On Thu, Aug 13, 2026 at 11:53:46AM -0700, Andrew Morton wrote: > > > You'll be mortified to hear that Sashiko wasn't able to find anything > > > to which to apply this. > > > > :)) > > > > Well, when it's right it's useful, when it's wrong or suggesting unrelated > > what-nots it's less useful :>) > > > > I do locally put things through claude + Chris Mason's prompts a lot, I > > don't always invoke local sashiko as it's very slow and token-heavy or has > > been so far, but am planning to do that more also in future. > > > > > > > > Sashiko can be guided with a base-commit: tag but I'm not sure how to > > > tell it what tree/branch to try, or even if that's necessary. Perhaps > > > someone can figure this out sometime. > > > > b4 gives a base commit, but I think because the trees are rebased it ends > > up being the incorrect one. > > It's not only that the tree is rebased, but also that mm-unstable carries > the previous version of the patches.
Yeah that's part of the issue, I can't rebase on mm-unstable as a result obviously. Is hard to know what is sensible to rebase on - if I rebase on base of my old version of the series in mm-unstable that'll probably be a bogus commit at some point due to other rebasing. > > > Not sure what the solution is! > > > > -- > > Cheers, Lorenzo > > -- > Sincerely yours, > Mike. -- Cheers, Lorenzo
