From: Kalle Valo <kvalo@kernel.org>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Missing Patchwork entries
Date: Tue, 22 Aug 2023 16:52:34 +0300 [thread overview]
Message-ID: <87350bi3q5.fsf@kernel.org> (raw)
In-Reply-To: <0659b81b-0d1f-7797-7968-f81a0e5df365@yandex.ru> (Dmitry Antipov's message of "Tue, 22 Aug 2023 16:39:52 +0300")
(adding linux-wireless so others can learn as well)
Dmitry Antipov <dmantipov@yandex.ru> writes:
> Hello,
>
> has Patchwork experienced some technical problems in the second half
> of June? Below is what I'm seeing at
> https://patchwork.kernel.org/project/linux-wireless/list/?page=2, and
> there is a visible gap between 2023-06-16 and 2023-06-29.
Your filter is set to show only New and Under Review states. If you
change the filter to show all states when you can see lots of patches
from that period:
https://patchwork.kernel.org/project/linux-wireless/list/?state=*&page=8
Unfortunately patchwork is not very intuitive to use and has pitfalls
like this.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
parent reply other threads:[~2023-08-22 13:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <0659b81b-0d1f-7797-7968-f81a0e5df365@yandex.ru>]
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=87350bi3q5.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=dmantipov@yandex.ru \
--cc=linux-wireless@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 NNTP newsgroup(s).