From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, brian.johnson@hpe.com,
tlaronde@polynum.com, Gerd Hoffmann <kraxel@redhat.com>
Cc: Andrew Fish <afish@apple.com>,
Leif Lindholm <quic_llindhol@quicinc.com>,
Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] edk2setup.sh shortcomings
Date: Thu, 2 Feb 2023 16:06:13 -0700 [thread overview]
Message-ID: <f084ec54-fa80-9bce-2be2-fc124ae725cb@bsdio.com> (raw)
In-Reply-To: <f5b016ef-4641-2875-1704-c71407ec1577@hpe.com>
On 2/2/23 14:49, Brian J. Johnson wrote:
> Hum... There is a very lethal weapon actually in use: the pillow. I
> already sent various patches and they are silently ignored...
>
> If my contribution will be ignored as others have been till now, honesty
> should be to clearly state: "we don't care and we won't care" so that
> I can use my time trying to solve the problems I want to address at a
> different level than UEFI...
I prefer to think that patches I've submitted are _missed_ rather than
ignored. It's still frustrating to realize that patches I've sent 6
months ago were never committed, even if they were reviewed.
I suspect part of the problem is that many people working on edk2 are in
companies which use Outlook, which can make keeping track of high
traffic mailing lists difficult.
And even in Thunderbird, if all edk2-devel emails go into a single
folder it can be difficult to keep track of patches.
I'm hoping that moving to Github PRs will improve things, with queries
like "is:open is:pr review-requested:@me" letting people easily find PRs
that need attention - though the UI looks like it could use some work to
allow people to save their queries etc.
--
Rebecca Cran
next prev parent reply other threads:[~2023-02-02 23:06 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 [this message]
2023-02-03 10:02 ` Marvin Häuser
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=f084ec54-fa80-9bce-2be2-fc124ae725cb@bsdio.com \
--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