AUH attaches not just the patch (if it was possible to produce), but also buildhistory and build failure logs (if something failed). It also provides a bit of explanation/context/apply-resend instructions in the email text. We can certainly consider options, I'm just not sure how to arrange all that if patches are sent directly as emails.
Note that the whole patchset is also attached as a tarball to overall AUH status email, and both the tarballs and their content are also available online: https://autobuilder.yocto.io/pub/auh/ Alex On Sat, 3 Jun 2023 at 01:49, Tim Orling <ticot...@gmail.com> wrote: > > In the `b4 shazaam` workflow, you cannot consume patches from AUH emails > because they are sent as attachments. This means a maintainer must first > download the patch from an email or wget it from a lore.kernel.org copied url. > > Before I go implementing something that might be unwanted, is there a > downside to sending AUH generated emails with the patches in the normal `git > send-email` type approach? > > Regards > --Tim
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60170): https://lists.yoctoproject.org/g/yocto/message/60170 Mute This Topic: https://lists.yoctoproject.org/mt/99297388/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
