From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
Florian Weimer <fweimer@redhat.com>,
Siddhesh Poyarekar <siddhesh@redhat.com>,
Arjun Shankar <ashankar@redhat.com>,
"H.J. Lu" <hjl.tools@gmail.com>,
Noah Goldstein <goldstein.w.n@gmail.com>,
Patrick McGehearty <patrick.mcgehearty@oracle.com>
Subject: Conflict with Monday patch review meeting.
Date: Sun, 23 Oct 2022 23:52:22 -0400 [thread overview]
Message-ID: <444019e1-cc04-39b7-89fa-d85a706702cf@redhat.com> (raw)
I have a conflict tomorrow morning with the 9am patch review meeting,
but the conference bridge will be open for anyone to attend and discuss
patch review.
My own SLI is at 130 days today. That is 130 days is the average time
it takes for a patch in patchwork to reach terminal state. I'm happy to
see that number keep dropping, and I want to keep working to ensure that
it moves down and tailor my own behaviors to try improve our patch review
process.
Please feel free to update the wiki with any notes taken during the meeting:
https://sourceware.org/glibc/wiki/PatchworkReviewMeetings
--
Cheers,
Carlos.
reply other threads:[~2022-10-24 3:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-all 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=444019e1-cc04-39b7-89fa-d85a706702cf@redhat.com \
--to=carlos@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=ashankar@redhat.com \
--cc=fweimer@redhat.com \
--cc=goldstein.w.n@gmail.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=patrick.mcgehearty@oracle.com \
--cc=siddhesh@redhat.com \
--cc=szabolcs.nagy@arm.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).