From: Matthew Hall <mhall@mhcomputing.net>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] Missing Outstanding Patches (By Me) In Patchwork
Date: Tue, 19 Jan 2016 21:33:45 -0800 [thread overview]
Message-ID: <569F1C39.6040800@mhcomputing.net> (raw)
In-Reply-To: <569F1927.7060608@mhcomputing.net>
I should have mentioned. I suspect it must be missing some variations of
the PATCH subject line when it goes to pickup patches, as I am sending
them using git send-email but they still don't appear inside of
Patchwork. Or there is some way of deactivating or deleting which does
not send me any notification, as I checked the date of the patches and
my name and other such searches but nothing appears at all.
I should also point out that issues like this could be avoided if we had
some more sophisticated ways of tracking and reviewing contributions
available such at GitHub, ReviewBoard, etc. as Patchwork seems rather
old and difficult to use from my experience with it so far.
Sincerely,
Matthew.
On 1/19/16 9:20 PM, Matthew Hall 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.
next prev parent reply other threads:[~2016-01-20 5:33 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 [this message]
2016-01-20 8:24 ` Andriy Berestovskyy
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=569F1C39.6040800@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.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).