From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: bpf <bpf@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
"David S. Miller" <davem@davemloft.net>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
workflows@vger.kernel.org
Subject: patch review delays
Date: Fri, 25 Oct 2019 07:50:22 -0700 [thread overview]
Message-ID: <CAADnVQK2a=scSwGF0TwJ_P0jW41iqnv6aV3FZVmoonRUEaj0kQ@mail.gmail.com> (raw)
The last few days I've experienced long email delivery when I was not
directly cc-ed on patches.
Even right now I see some patches in patchworks, but not in my inbox.
Few folks reported similar issues.
In order for everyone to review the submissions appropriately
I'll be applying only the most obvious patches and
will let others sit in the patchworks a bit longer than usual.
Sorry about that.
Ironic that I'm using email to talk about email delays.
My understanding that these delays are not vger's fault.
Some remediations may be used sporadically, but
we need to accelerate our search of long term solutions.
I think Daniel's l2md:
https://git.kernel.org/pub/scm/linux/kernel/git/dborkman/l2md.git/
is a great solution.
It's on my todo list to give it a try,
but I'm not sure how practical for every patch reviewer on this list
to switch to that model.
Thoughts?
next reply other threads:[~2019-10-25 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 14:50 Alexei Starovoitov [this message]
2019-10-25 16:34 ` patch review delays Konstantin Ryabitsev
2019-10-25 18:27 ` Eric Wong
2019-10-25 22:39 ` Eric Wong
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='CAADnVQK2a=scSwGF0TwJ_P0jW41iqnv6aV3FZVmoonRUEaj0kQ@mail.gmail.com' \
--to=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=konstantin@linuxfoundation.org \
--cc=netdev@vger.kernel.org \
--cc=workflows@vger.kernel.org \
/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).