Re: Parsing git send-email

From: Tom Isaacson <tom.isaacson@teknique.com>
Date: Jul 22, 2023, 21:21 UTC
Message-ID: <CA+EiEZLKkaX78y74xWQMioSyvwFgD7m9K-Pad14dbZSXKGuFNQ@mail.gmail.com>
In-Reply-To: <20230717-upscale-repacking-a56622@meerkat>

We use Yocto at work and try to help out with the project. I read this and the linked articles and one piece in https://www.linux.com/audience/maintainer-confidential-opportunities-and-challenges-of-the-ubiquitous-but-under-resourced-yocto-project/ caught my eye:

> 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.

It seemed like someone must have solved this problem already so I looked around and found https://gitgitgadget.github.io/, which is what this mailing list uses. Yocto already uses https://github.com/getpatchwork/patchwork to monitor patches sent to the mailing list. I was wondering if there are any other similar projects I haven't heard of.

On Tue, Jul 18, 2023 at 2:05 AM Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:

Show 12 quoted lines

>
> On Sun, Jul 16, 2023 at 11:22:20AM +1200, Tom Isaacson wrote:
> > I'm trying to find a way of parsing emails sent by "git send-email".
> > Does anyone know of any existing solutions?
>
> Define parsing?
>
> If you just want patch/description/header information, the easiest is to use
> git-mailinfo. If you want to do something more than that, then you need to
> give additional information regarding what your end-goal is.
>
> -K

-- 
Tom Isaacson