From: "Marvin Häuser" <mhaeuser@posteo.de>
To: Rebecca Cran <rebecca@bsdio.com>,devel@edk2.groups.io
Subject: Re: [edk2-devel] edk2setup.sh shortcomings
Date: Fri, 03 Feb 2023 02:02:49 -0800 [thread overview]
Message-ID: <17027.1675418569211847080@groups.io> (raw)
In-Reply-To: <f084ec54-fa80-9bce-2be2-fc124ae725cb@bsdio.com>
[-- Attachment #1: Type: text/plain, Size: 585 bytes --]
Getting a patch reviewed by one maintainer and having the rest not respond even after multiple(!) pings is not „missed“. Let‘s be realistic here.
When I was still actively subscribed to the list, I had all mails that CC‘d me go to a separate folder. If I had more patch traffic, I would have had two (patch and non-patch mails) or more folders. At least in theory, everyone can organise their inbox as they please.
The edk2 build system stack is pretty inconvenient at times. Voluntary contributions such as this should be proactively endorsed.
Best regards,
Marvin
[-- Attachment #2: Type: text/html, Size: 641 bytes --]
next prev parent reply other threads:[~2023-02-03 10:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 11:29 edk2setup.sh shortcomings tlaronde
2023-02-02 16:50 ` [edk2-devel] " Gerd Hoffmann
2023-02-02 17:59 ` tlaronde
2023-02-02 21:49 ` Brian J. Johnson
2023-02-02 23:06 ` Rebecca Cran
2023-02-03 10:02 ` Marvin Häuser [this message]
2023-02-03 12:29 ` tlaronde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17027.1675418569211847080@groups.io \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox