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 Paul, On Sun, Jan 12, 2020 at 10:47 PM Paul Spooren <m...@aparcar.org> wrote: > > Hi all, > > some time ago I created a (now outdated) device overview[0] based on > YAML meta data. This approach could simplify maintaining an device > overview and device specific pages[1]. > > All commits adding new devices already include most relevant information > for creating the overview. However it would be convenient if developers > would format their commit messages in a generic format, therefore I'd > propose the following: > > Every commit message for newly added devices must contain a number of > hardware information and steps for an initial installation. > The hardware information should contain at least the following > information, maybe more: > > SoC, flash, ram, wifi, LEDs, buttons, USB, serial, vendor, model, device > tree ID, Ethernet ports can we automate this somehow? the device tree files already contain most of that information. (I'm all for providing good data for the TOH but I'm challenging the idea of doing this manually) Martin
--- End Message ---
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
