The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped automatically by the mailing list software.
--- Begin Message ---Am 7. Februar 2024 11:53:55 MEZ schrieb Jonas Gorski <jonas.gor...@gmail.com>: >On Wed, 7 Feb 2024 at 02:48, Elliott Mitchell <ehem+open...@m5p.com> wrote: >> >> 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. > >Why is this script needed? What exactly does it do? Does it preserve >bisectability? How would you use it? I see neither a help message nor >any usage examples. > >Please provide more detailed explanation in the commit message, >especially since perl isn't the most common or easy to read language. > >Regards, >Jonas > >_______________________________________________ >openwrt-devel mailing list >openwrt-devel@lists.openwrt.org >https://lists.openwrt.org/mailman/listinfo/openwrt-devel This might be of help <https://lists.openwrt.org/pipermail/openwrt-devel/2023-October/041672.html> Elliott linked it in his previous mail. It explains the problem fairly well. Short version: Right now every new kernel version creates a new kernel config file as a copy of the old one which doesn't preserve the git history which hinders the usage of git blame. git bisect should still work fairly well even without the change. Regards Felix
--- End Message ---
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel