{"thread":{"id":"59991","subject":"Parsing git send-email","startedAt":"2023-07-15T23:22:33Z","lastAt":"2023-07-22T21:21:41Z","messageCount":3,"participants":["Tom Isaacson","Konstantin Ryabitsev"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"479549","messageId":"CA+EiEZ+PBLEtQ1bD_TnsstT0jNehAs2CGgYXebEE4aweK=kmgg@mail.gmail.com","threadId":"59991","inReplyTo":null,"subject":"Parsing git send-email","fromName":"Tom Isaacson","fromEmail":"tom.isaacson@teknique.com","sentAt":"2023-07-15T23:22:20Z","receivedAt":"2023-07-15T23:22:33Z","isPatch":false,"sender":{"key":"tom.isaacson@teknique.com","avatar":null},"body":"I'm trying to find a way of parsing emails sent by \"git send-email\".\nDoes anyone know of any existing solutions?\n\nThanks.\n\n-- \nTom Isaacson\n"},{"id":"479573","messageId":"20230717-upscale-repacking-a56622@meerkat","threadId":"59991","inReplyTo":"CA+EiEZ+PBLEtQ1bD_TnsstT0jNehAs2CGgYXebEE4aweK=kmgg@mail.gmail.com","subject":"Re: Parsing git send-email","fromName":"Konstantin Ryabitsev","fromEmail":"konstantin@linuxfoundation.org","sentAt":"2023-07-17T14:05:18Z","receivedAt":"2023-07-17T14:05:37Z","isPatch":false,"sender":{"key":"konstantin@linuxfoundation.org","avatar":"https://gravatar.com/avatar/7cb8827c6de56e1bd2dea16508c6708aa43feed3bf3813bcdacecdf96ceadd79?d=mp&s=160"},"body":"On Sun, Jul 16, 2023 at 11:22:20AM +1200, Tom Isaacson wrote:\n> I'm trying to find a way of parsing emails sent by \"git send-email\".\n> Does anyone know of any existing solutions?\n\nDefine parsing?\n\nIf you just want patch/description/header information, the easiest is to use\ngit-mailinfo. If you want to do something more than that, then you need to\ngive additional information regarding what your end-goal is.\n\n-K\n"},{"id":"479776","messageId":"CA+EiEZLKkaX78y74xWQMioSyvwFgD7m9K-Pad14dbZSXKGuFNQ@mail.gmail.com","threadId":"59991","inReplyTo":"20230717-upscale-repacking-a56622@meerkat","subject":"Re: Parsing git send-email","fromName":"Tom Isaacson","fromEmail":"tom.isaacson@teknique.com","sentAt":"2023-07-22T21:21:28Z","receivedAt":"2023-07-22T21:21:41Z","isPatch":false,"sender":{"key":"tom.isaacson@teknique.com","avatar":null},"body":"We use Yocto at work and try to help out with the project. I read this\nand the linked articles and one piece in\nhttps://www.linux.com/audience/maintainer-confidential-opportunities-and-challenges-of-the-ubiquitous-but-under-resourced-yocto-project/\ncaught my eye:\n> One question that comes up a lot is the project’s development model. We’re an “old school” patch on a mailing list, similar to the kernel. New developers complain that we should have GitHub workflows so they can make point-and-click patch submissions. I have made submissions to other projects that way, and I can see the attraction of it. Equally, it does depend a lot on your review requirements. We want many people to see our patches, not just one person, and we greatly benefit from that comprehensive peer review.\n\nIt seemed like someone must have solved this problem already so I\nlooked around and found https://gitgitgadget.github.io/, which is what\nthis mailing list uses. Yocto already uses\nhttps://github.com/getpatchwork/patchwork to monitor patches sent to\nthe mailing list. I was wondering if there are any other similar\nprojects I haven't heard of.\n\n\nOn Tue, Jul 18, 2023 at 2:05 AM Konstantin Ryabitsev\n<konstantin@linuxfoundation.org> wrote:\n>\n> On Sun, Jul 16, 2023 at 11:22:20AM +1200, Tom Isaacson wrote:\n> > I'm trying to find a way of parsing emails sent by \"git send-email\".\n> > Does anyone know of any existing solutions?\n>\n> Define parsing?\n>\n> If you just want patch/description/header information, the easiest is to use\n> git-mailinfo. If you want to do something more than that, then you need to\n> give additional information regarding what your end-goal is.\n>\n> -K\n\n\n\n-- \nTom Isaacson\n"}]}