From: Andriy Berestovskyy <aber@semihalf.com>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Missing Outstanding Patches (By Me) In Patchwork
Date: Wed, 20 Jan 2016 09:24:34 +0100 [thread overview]
Message-ID: <CAOysbxon-aZANqJ6E5Zg=zEYztT0bhYLzbekK6oz7BHkxO6WJw@mail.gmail.com> (raw)
In-Reply-To: <569F1927.7060608@mhcomputing.net>
Hi Matthew,
I hope that is what you are looking for:
http://dpdk.org/dev/patchwork/project/dpdk/list/?submitter=37&state=*&archive=both
You just click on Filters and there are few options...
Andriy
On Wed, Jan 20, 2016 at 6:20 AM, Matthew Hall <mhall@mhcomputing.net> wrote:
> I have some outstanding minor patches which do not appear in Patchwork
> anywhere I can see but the interface is also pretty confusing.
>
> Is there a way to find all patches by a person throughout time so I can see
> what happened to them and check why they are not listed and also not merged
> (that I am aware of anyway)?
>
> Sincerely,
> Matthew.
--
Andriy Berestovskyy
prev parent reply other threads:[~2016-01-20 8:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 5:20 Matthew Hall
2016-01-20 5:33 ` Matthew Hall
2016-01-20 8:24 ` Andriy Berestovskyy [this message]
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='CAOysbxon-aZANqJ6E5Zg=zEYztT0bhYLzbekK6oz7BHkxO6WJw@mail.gmail.com' \
--to=aber@semihalf.com \
--cc=dev@dpdk.org \
--cc=mhall@mhcomputing.net \
/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).