On Sat, Mar 23, 2024 at 07:56:01PM +0100, Stijn Segers wrote: > > Op zondag 3 maart 2024 om 15:24:50 -08:00:00 schreef Elliott Mitchell > <ehem+open...@m5p.com>: > > Date: Tue, 6 Feb 2024 17:16:41 -0800 > > > > Create a script for automating kernel version changes. This > > generates a pair of commits which cause history to remain attached to > > all versioned configuration files. > > > > Crucially this makes `git blame` work without needing > > --find-copies-harder, which is too slow for routine use. This also > > updates *everything*, which greatly simplifies rebasing patches > > which effect multiple devices. > > > > Credit to Christian Marangi who knew of the technique: > > <https://lists.openwrt.org/pipermail/openwrt-devel/2023-October/041672.html> > > > > Signed-off-by: Elliott Mitchell <ehem+open...@m5p.com> > > > Is there a way to bump a specific target to a new kernel with your > script? It doesn't look like it, but I might be mistaken. Would it be a > lot of work to integrate that? With the shell equivalent being merged, > I can understand any reluctance to adding this functionality, but it's > worth asking.
As originally written, no. I see significant advantages to that approach and it really is starting to look like the best balance. To add the ability to handle a single target, near trivial. To add the ability to do multiple target(s), very simple. To do this efficiently, still fairly simple. It does seem this list has become useless for patch submission, so it has been brought onto GitHub: https://github.com/openwrt/openwrt/pull/14907 -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | ehem+sig...@m5p.com PGP 87145445 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445 _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
