similar to: [LLVMdev] Announcement: Phabricator for code reviews

You might want to mention other functionality, like Herald, which I think fills a need that a lot of developers have. Well, I guess since this message is on the list, I can just say: Phabricator's "Herald" tool lets you (among other things) set up actions to happen in response to certain events; one huge use case for this is setting up alerts when parts of the tree that you are

On Wed, Oct 17, 2012 at 8:25 PM, Sean Silva <silvas at purdue.edu> wrote: > You might want to mention other functionality, like Herald, which I > think fills a need that a lot of developers have. > > Well, I guess since this message is on the list, I can just say: > Phabricator's "Herald" tool lets you (among other things) set up > actions to happen in

On Wed, Oct 17, 2012 at 10:18 AM, Manuel Klimek <klimek at google.com> wrote: > Dear LLVM / Clang community, > > we'd like to open the use of Phabricator as an optional tool for doing code > reviews to a wider audience. Please feel free to start your code reviews by > following the documentation at http://llvm.org/docs/Phabricator.html. > > Note that e-mail is still

On Fri, Oct 19, 2012 at 1:05 AM, Michael Spencer <bigcheesegs at gmail.com>wrote: > On Wed, Oct 17, 2012 at 10:18 AM, Manuel Klimek <klimek at google.com> wrote: > > Dear LLVM / Clang community, > > > > we'd like to open the use of Phabricator as an optional tool for doing > code > > reviews to a wider audience. Please feel free to start your code

> Dear LLVM / Clang community, > > we'd like to open the use of Phabricator as an optional tool for doing code > reviews to a wider audience. Please feel free to start your code reviews by > following the documentation at > http://llvm.org/docs/Phabricator.html. > > > Note that e-mail is still the reference medium for code reviews. Please let > me know about

On Fri, Jun 27, 2014 at 8:13 AM, Yaron Keren <yaron.keren at gmail.com> wrote: > Happened to me twice, it would be really nice if Phab would require > confirmation of patches created without CCing one of the two lists, > something like: > > "You have not CCed llvm-commits or cfe-commits, are you creating a private > patch?" > I filed

On Fri, Oct 19, 2012 at 1:25 AM, Johan Bergström <bugs at bergstroem.nu> wrote: > > Dear LLVM / Clang community, > > > > we'd like to open the use of Phabricator as an optional tool for doing > code > > reviews to a wider audience. Please feel free to start your code reviews > by > > following the documentation at > >

Hey, On 20/10/2012, at 7:19 AM, Manuel Klimek <klimek at google.com> wrote: > On Fri, Oct 19, 2012 at 1:25 AM, Johan Bergström <bugs at bergstroem.nu> wrote: > > Dear LLVM / Clang community, > > > > we'd like to open the use of Phabricator as an optional tool for doing code > > reviews to a wider audience. Please feel free to start your code reviews by

On Thu, Jun 26, 2014 at 11:34 AM, Daniel Sanders <Daniel.Sanders at imgtec.com> wrote: > > As I understand, some people legitimately use Phabricator for internal > > review, ... > > MIPS currently do this for patches that only touch the MIPS backend > (details can be found at > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20140602/220385.html). >

In a recent review via Phabricator, I was receiving bounce notifications for mail being sent to llvm-commits because of "Too many recipients to the message", even though I am a subscriber. I wonder how common is that. On Wed, Jun 25, 2014 at 12:03 PM, Manuel Klimek <klimek at google.com> wrote: > I am prioritizing email issues. Please always make sure to send them >

Moving this to llvmdev - it needs a bit of a wider audience. There are several issues with phabricator, and in the current state of things there's a huge amount of confusion on how to even report problems, let alone try to resolve them. Recently I started a thread about empty emails, was directed to the phabricator project's bug tracker, and told there that LLVM has customized

Hi Manuel, I like Phabricator for code review much much more than emails. Let me know how I can help (I’m not afraid of PHP). — Mehdi > On May 27, 2015, at 3:12 AM, Manuel Klimek <klimek at google.com> wrote: > > Quick update from IRC chat: > Justin (and anybody else who wants to) is going to file bugs against our phab workflow on the llvm-bugtracker until we get a

On Sat, Jun 1, 2019 at 5:29 AM <paul.robinson at sony.com> wrote: > One particular change: I've disabled notifications for the duplicate > Subversion meta-repos... so, for example, a commit to Clang will still get > 2 notifications (rL and rG). Before yesterday, this should have sent 3: one > each for rL, rG, and rC. Projects not in the monorepo will get > notifications

Files '.arcconfig' still contain reference to http://llvm-reviews.chandlerc.com/, so arcanist doesn't work. Thanks, --Serge 2014-04-06 3:11 GMT+07:00 Manuel Klimek <klimek at google.com>: > On Sat, Apr 5, 2014 at 8:42 PM, Manuel Klimek <klimek at google.com> wrote: > >> Short update - the sending to the *-commits lists doesn't work yet - I'm >>

On Mon, Jun 22, 2020 at 2:33 AM Manuel Klimek <klimek at google.com> wrote: > On Fri, Jun 19, 2020 at 10:04 PM Mehdi AMINI via cfe-dev < > cfe-dev at lists.llvm.org> wrote: > >> >> >> On Fri, Jun 19, 2020 at 9:56 AM Hubert Tong via llvm-dev < >> llvm-dev at lists.llvm.org> wrote: >> >>> On Fri, Jun 19, 2020 at 12:32 PM Anton

On Mon, Jun 22, 2020 at 9:25 PM David Blaikie <dblaikie at gmail.com> wrote: > On Mon, Jun 22, 2020 at 8:15 PM Mehdi AMINI via cfe-dev > <cfe-dev at lists.llvm.org> wrote: > > > > > > > > On Mon, Jun 22, 2020 at 2:33 AM Manuel Klimek <klimek at google.com> wrote: > >> > >> On Fri, Jun 19, 2020 at 10:04 PM Mehdi AMINI via cfe-dev

Short update - the sending to the *-commits lists doesn't work yet - I'm currently working on fixing that (basically getting reviews at reviews.llvm.orgsubscribed to the list) On Sat, Apr 5, 2014 at 8:37 PM, Renato Golin <renato.golin at linaro.org>wrote: > Nice work! It's a lot faster now, thanks! > > --renato > > PS: I'm not really bothered with a redirect

Hi Manuel, > we'd like to open the use of Phabricator as an optional tool for doing code > reviews to a wider audience. Please feel free to start your code reviews by > following the documentation at http://llvm.org/docs/Phabricator.html. sorry for the silly question but... how do you sign up? The "sign up" section doesn't have a "sign up here" link. It

Hi Manuel, Thanks for the help. Still persists for me too. Instead of waiting indefinitely, now I get this error: Unhandled Exception ("AphrontDeadlockQueryException") #1205: Lock wait timeout exceeded; try restarting transaction On Thu, Dec 11, 2014 at 11:26 AM, suyog sarda <sardask01 at gmail.com> wrote: > The problem still persist :( > > On 12/11/14, Manuel Klimek

On Fri, Jun 19, 2020 at 9:56 AM Hubert Tong via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Fri, Jun 19, 2020 at 12:32 PM Anton Korobeynikov via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Just my 2 cents here: we are working on enabling this as a part of >> bugzilla migration as PRs and issues are very tied inside GitHub. Stay >> tuned for