* Parsing git send-email
@ 2023-07-15 23:22 Tom Isaacson
2023-07-17 14:05 ` Konstantin Ryabitsev
0 siblings, 1 reply; 3+ messages in thread
From: Tom Isaacson @ 2023-07-15 23:22 UTC (permalink / raw)
To: git
I'm trying to find a way of parsing emails sent by "git send-email".
Does anyone know of any existing solutions?
Thanks.
--
Tom Isaacson
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Parsing git send-email
2023-07-15 23:22 Parsing git send-email Tom Isaacson
@ 2023-07-17 14:05 ` Konstantin Ryabitsev
2023-07-22 21:21 ` Tom Isaacson
0 siblings, 1 reply; 3+ messages in thread
From: Konstantin Ryabitsev @ 2023-07-17 14:05 UTC (permalink / raw)
To: Tom Isaacson; +Cc: git
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Parsing git send-email
2023-07-17 14:05 ` Konstantin Ryabitsev
@ 2023-07-22 21:21 ` Tom Isaacson
0 siblings, 0 replies; 3+ messages in thread
From: Tom Isaacson @ 2023-07-22 21:21 UTC (permalink / raw)
To: Konstantin Ryabitsev; +Cc: git
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:
>
> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-07-22 21:21 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-07-15 23:22 Parsing git send-email Tom Isaacson
2023-07-17 14:05 ` Konstantin Ryabitsev
2023-07-22 21:21 ` Tom Isaacson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).