<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 25, 2014 at 11:10 AM, Alp Toker <span dir="ltr"><<a href="mailto:alp@nuanti.com" target="_blank">alp@nuanti.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
On 25/06/2014 21:03, Eli Bendersky wrote:<div><div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, Jun 25, 2014 at 10:44 AM, Alp Toker <<a href="mailto:alp@nuanti.com" target="_blank">alp@nuanti.com</a> <mailto:<a href="mailto:alp@nuanti.com" target="_blank">alp@nuanti.com</a>>> wrote:<br>
<br>
For whatever reason, patches posted to the Phabricator website<br>
still aren't being sent to the mailing list, making it difficult<br>
for us to review them.<br>
<br>
I've raised this issue a couple of times in the last few weeks.<br>
<br>
In practice this has a detrimental effect to the development<br>
workflow because it means that code is being seen only by a small<br>
group of individuals who have web accounts. The code isn't hitting<br>
llvm-commits or cfe-commits where the majority of code maintainers<br>
use the mailing lists for review.<br>
<br>
At this point I think Phabricator should be disabled and patches<br>
should be send to the mailing lists *until* the technical issue is<br>
confirmed resolved.<br>
<br>
It's really uncool that code is entering ToT through this<br>
back-channel -- I appreciate that it might not be intentional, but<br>
every single patch that gets committed this way is a real problem<br>
for the project.<br>
<br>
<br>
Phabricator has certainly had its share of technical difficulties lately. Just last week it suppressed all email to llvm-commits for many hours. These problems should be solved. That said, talking of "private reviews" and "back-channels" doesn't strike me as constructive.<br>
</blockquote>
<br></div></div>
Eli, I wasn't making a value judgement. That's exactly what they are:<br>
<br>
1) They're private reviews because they're conducted away from the LLVM community.<br>
2) It's a back-channel because the only means of veto is to revert the patch or attempt to "fix forward" post-commit.<br>
<br>
I already pointed out that it may not be intentional -- </blockquote><div><br></div><div>"May" not be intentional suggests that it also "may" be intentional. Or is it English comprehension failing me? [sorry, 3rd language...]</div>
<div><br></div><div>When llvm-commits is CCd on the Phabricator review, any suggestion of intentional hiding is not only inappropriate, but also somewhat ridiculous. Unless you're suggesting someone is planting those PHP bugs? [that could be unintentional, I concede, since PHP is just one big bug in general]</div>
<div><br></div><div>Again, no disagreement whatsoever that the bugginess is harmful and should be addressed. But the tone could be friendlier.</div><div><br></div><div>Eli</div><div><br></div><div><br></div></div></div></div>