search for: d23393

...re I am. The reason I'm here is that I came across a doc bug, I spent quite a bit of time learning all the tips and tricks for submitting patches to llvm including using phabricator and finally tweeting at the llvm account to get some attention. The patch is here: https://reviews.llvm.org/D23393 I looked in git and it doesn't look like this was pulled in. Has it been accepted? If no, did I miss some step? Thanks, -Alfred

...t I came across a doc bug, I spent quite a bit of time learning >> all the tips and tricks for submitting patches to llvm including using >> phabricator and finally tweeting at the llvm account to get some attention. >> >> The patch is here: >> https://reviews.llvm.org/D23393 >> >> I looked in git and it doesn't look like this was pulled in. Has it been >> accepted? If no, did I miss some step? >> >> http://llvm.org/viewvc/llvm-project?rev=281297&view=rev >> Thanks Davide!! -Alfred

On 9/13/16 1:04 AM, David Chisnall via llvm-dev wrote: > On 13 Sep 2016, at 08:45, Alex Bradbury via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> 2) Arguably, Phabricator provides a confusing interface for first-time >> or irregular users. > I don’t think it’s fair to say that the Phabricator interface is confusing for first-time or irregular users. I use Phabricator on

On 13 September 2016 at 07:59, Piotr Padlewski via llvm-dev <llvm-dev at lists.llvm.org> wrote: > This is exactly why we should switch to github. It is much easier for new > contributors to start with small fixes. There are two really quite separate issues here: 1) Patches, even trivial ones can sit unreviewed for long periods of time leading to a negative first time contribution