All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: 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: Re: patch review delays
Date: Fri, 25 Oct 2019 18:27:12 +0000	[thread overview]
Message-ID: <20191025182712.GA9391@dcvr> (raw)
In-Reply-To: <CAADnVQK2a=scSwGF0TwJ_P0jW41iqnv6aV3FZVmoonRUEaj0kQ@mail.gmail.com>

Alexei Starovoitov <alexei.starovoitov@gmail.com> wrote:
> 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?

If cloning git repos is too much work, You can subscribe to an
Atom feed of search results to paths or files you're interested
in using "dfn:" (diff-file-name) using your favorite feed
reader:

lore.kernel.org/lkml/?q=dfn:path/to/dir-or-file-youre-interested-in&x=A

Or drop the "&x=A" to get an HTML summary, or POST to that URL
with "&x=m" to download an mbox.

You can also search for multiple files at once by having dfn:foo
multiple times separated by "OR"

lore.kernel.org/lkml/?q=dfn:foo+OR+dfn:bar&x=A

https://lore.kernel.org/lkml/_/text/help/ has other prefixes
like "dfn:" which might be helpful for search.

For example, if you expected to be Cc-ed (or To-ed) and want to
double-check that your mail account got it, you can use the "c:"
or "tc:" prefixes with your name or address, too.

  parent reply	other threads:[~2019-10-25 18:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-25 14:50 patch review delays Alexei Starovoitov
2019-10-25 16:34 ` Konstantin Ryabitsev
2019-10-25 18:27 ` Eric Wong [this message]
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=20191025182712.GA9391@dcvr \
    --to=e@80x24.org \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.