Thanks. I have gone that route and there was no response.
What constitutes 'particularly urgent'?
In regards to D30107<https://reviews.llvm.org/D30107> it some fairly
obvious defect(s) and there are a few bugs open in your database about the
issue,
but it seems an area that doesn't get much interest (related to
DynamicLibrary class).
Thanks again.
________________________________
From: Robinson, Paul <paul.robinson at sony.com>
Sent: Tuesday, March 7, 2017 6:35 PM
To: Frederich Munch
Cc: llvm-dev at lists.llvm.org
Subject: RE: Restarting a stalled patch
Standard practice is to add a comment yourself that says "Ping"
(people don't mind a pace of about 1/week, more if it is particularly
urgent).
http://llvm.org/docs/DeveloperPolicy.html#code-reviews
LLVM Developer Policy — LLVM 5
documentation<http://llvm.org/docs/DeveloperPolicy.html#code-reviews>
llvm.org
Making and Submitting a Patch ¶ When making a patch for review, the goal is to
make it as easy for the reviewer to read it as possible. As such, we recommend
that you:
--paulr
From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of
Frederich Munch via llvm-dev
Sent: Tuesday, March 07, 2017 10:23 AM
To: llvm-dev
Subject: [llvm-dev] Restarting a stalled patch
Hello,
I was curious if there was any advice on how to get a code-review
restarted/completed. The two I've submitted recently
(D30107<https://reviews.llvm.org/D30107>
D29923<https://reviews.llvm.org/D29923>) have gotten a bit of review but
both then seem to stall. Any hints?
Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170307/74eb3cab/attachment.html>