Elliott Mitchell

Simply rebased onto `openwrt/main`. Seems another approach to this is to do: ``` git fetch github pull/14280/head git rebase -i main FETCH_HEAD ```

Update to notes. The ones where order matters are db203ff92df148a44853e8abdead0c2f98ce2f42 and earlier. I'm getting increasingly worried about db203ff92df148a44853e8abdead0c2f98ce2f42 and the dependency, but the use of GNU Make in OpenWRT is...

Hmm, lost track of things. That slow download of ccache from S3 looks worrisome. The significant order is now c9fe6f4b25b6b89bb29edea3469c152c72598578 and earlier. The example is 6dc0b6ccfa5094e6890f3a8ae0add52f372c1516.

On second thought, might be best for a maintainer to quickly grab the script out of the commit and run: ``` scripts/update_kernel.pl -6.1 -6.6 git merge --ff-only scripts/update_kernel.pl -5.15 -6.6...

Quick check, 3 were using the other script, 3 were doing manual copy. While the ratio may improve in the future, that is a Bad Sign. Problem is it will...

> Take a look at this: #14713 Looks like someone beat you to it ;) [Not really so](https://lists.openwrt.org/pipermail/openwrt-devel/2024-February/042254.html) (notice the date on this). > Please provide an example so that...

I should ask since it came to mind when examining #14713. How are devices currently without 6.1 configurations expected to be handled? Will they be required to skip 6.1 and...

> NACK, I do not like it > > Using two times `-C` will make `git blame` to detect the moves: > > ``` > git blame -C -C target/linux/malta/config-6.1...

I'll be rebasing in a few hours, when I'll squash the third in. I've also got something others may like better for doing single device updates.

@hauke if you're truly that much against the idea, you'll need to revert 3561015efd. Otherwise most others think `git blame` being properly functional is kind of important.