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 ---Hi, > I believe this is a waste of resources and a very suboptimal approach. > I’m not sure I’m interested in spending time on this :P Probably it is. How would you approach it? Some devices that are the same hardware with just a different name are already supported like this: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=ac36cca012dd1bbeea0fc4c2dc7a00941de34b52 > > Some devices share the exact same hardware and differ only in > (marketing) name, as evidenced by: > https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=5ac974f2145c770431a6eb7e006dd086b70224b1 > > (this device uses the 911L platform) > >> Just have a look at how the few ath79 devices are implemented, but >> note that they will be moved to a mikrotik subtarget soon as >> indicated by Roger already. > > I’ve offered in this thread a couple patches to align the ath79 > implementation on the existing ramips one wrt mtd partitioning and naming. To me they're OK, I have no preference for having the partitions nested or not. What are the benefits and drawbacks? Cheers! > > Best, > Thibaut > > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel
--- End Message ---
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
