similar to: Phabricator subscribes non-clang projects to llvm-commit, but the commit hook still uses cfe-commits

I have been noticing odd behavior like that. I think it started with the auto-subscribe behavior when you specify a repository? --paulr From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Don Hinton via llvm-dev Sent: Monday, January 22, 2018 3:04 PM To: LLVM Development List Subject: [llvm-dev] Phabricator subscribes non-clang projects to llvm-commit, but the commit hook

PaulR (sorry again if this is known knowledge) > There's no reason for Herald to be adding project LLVM/subscriber llvm-commits at the last second here. Its possible the rL (LLVM) had be added as the repository in the review on creation rather than rCFE, if thats the case then the herald rule "H270" is going to fire because it see the repository in the review, so add LLVM

Forgot to mention: > Also, how would arcanist pick up two callsigns here? Wouldn't it just pick the from the closest surrounding .arcconfig? The review request will belong to a single repository, as you noticed (from the closest .arcconfig to where the arc command was invoked). However, when commits land, they will be imported under either one (rL for LLVM diffs) or two (rL + rC for e.g.

Does phabricator have a way of changing the default commit message template through the per-repo .arcconfig? Making the default template include the appropriate mailing list automatically might go a long way to mitigating our problems. It doesn't help when uploading through the web UI though. -- Sean Silva -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi Ben, (+llvm-dev since the email I'm replying to wasn't sent there) 2017-11-21 17:18 GMT+01:00 Ben Hamilton via cfe-dev <cfe-dev at lists.llvm.org> : > OK. I confirmed that Stephan's process to send out cross-repo diffs from > the monorepo is not affected by my proposal. > > I'm a bit late to the party, and I might just not have comprehended this correctly.

On Wed, Jun 25, 2014 at 3:30 PM, John Criswell <criswell at illinois.edu> wrote: > On 6/25/14, 5:15 PM, Vadim Chugunov wrote: > > 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. > > >

I have seen the "Too many recipients to the message" several times. A limit of 10 includes the patch author and the list leaving just 8 subscribers/reviewers is way too low. Given that these e-mails can be sent only by a Phab. user I'm not sure that spam is a problem at all: A potential spammer would first have to subscribe to Phab. then create a proper diff,... far easier just to

It seems like this has already been set up for all the projects except for libunwind. Can we create a Differential repository for it as well? I'll be happy to update its .arcconfig once that's done. On Mon, Nov 27, 2017 at 9:02 AM Ben Hamilton via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Forgot to mention: > > > > Also, how would arcanist pick up two callsigns

On 6/24/20 3:41 PM, Chris Lattner via llvm-dev wrote: >> When I looked into this possibility (GitHub PR) when we merged MLIR in the monorepo: just Herald rules was already a blocker and I couldn't find a replacement readily available on GitHub. The handling of stack of revisions on GitHub was another problem mentioned. > Fair enough - I haven’t investigated the technical issues with

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, Jun 24, 2020 at 2:31 AM Chris Lattner via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > On Jun 23, 2020, at 10:56 AM, Philip Reames via cfe-dev < > cfe-dev at lists.llvm.org> wrote: > > On 6/22/20 2:34 AM, Manuel Klimek via llvm-dev wrote: > > On Sat, Jun 20, 2020 at 1:45 AM Zachary Turner via llvm-dev < > llvm-dev at lists.llvm.org>

Hi Manuel, It's been brought to my attention that my usage of the Phabricator Audit tool to track which commits have been reviewed is causing a large number of (almost) empty emails to be sent to the commit authors and anyone else added to the audit as a reviewer. Presumably there are some state change emails that we haven't blocked yet (e.g. the 'Accept commit' and 'Resign

I am using openssh version 3.6p1 under AIX 5.1. I am trying to change the login herald. I have changed /etc/security/login.cfg, and when logging in via telnet, I see the new herald. When I log in through ssh, using public key authentication, I get the default herald. I am not sure if I am changing the correct file. If I have missed something in the documentation I apologize, but I don't see

+llvm-dev, so we get wider input :) Given how unfortunate reviews that are started without cc'ing the right list are (basically folks need to re-send the review from scratch), I support this idea. Ben, couldn't rL still be available for all projects? (and be the main project for LLVM). On Tue, Nov 21, 2017 at 5:18 PM Ben Hamilton via cfe-dev < cfe-dev at lists.llvm.org> wrote:

On Thu, Jan 23, 2020 at 9:30 AM Fedor Sergeev via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hubert, thank you so much for the detailed bisection of what I believe > is the most > problematic GitHub PR =<= Phab difference in terms of review process! > This thread has been focused on a specific aspect of the tooling / process, the thread we had two months ago mentioned

On Thu, Nov 23, 2017 at 12:58 AM Ben Hamilton <benhamilton at google.com> wrote: > Absolutely — I should have mentioned that we would keep the main rL > project and continue to use it. > Your original email said "Moving forward, only LLVM commits will be identified with the prefix rL (as in https://reviews.llvm.org/rL12345) — each project will get its own unique prefix, which

Friends- I have taken a new job and will be moving at the end of March. The newspaper I currently work for is looking for someone to take my place. I have really enjoyed working here. It is a great environment with very nice people to work with. And the best part is you get to develop in Ruby and Rails, for everything! The paper is willing to accept applications from people who would

Does anyone have a clue as to when the railsconf speakers will be announced? Thanks- -Ezra Zygmuntowicz Yakima Herald-Republic WebMaster http://yakimaherald.com 509-577-7732 ezra@yakima-herald.com

This looks great! One hitch though: it looks like I can monitor files by name but what I really want to watch is a whole directory "/llvm/trunk/include/llvm-c". I didn't see any way to do that. Do you have any idea if that is possible? I can add a rule for each file which is probably OK but then I'll miss any new files. Best, Keith On Wed, Oct 17, 2012 at 2:25 PM, Sean Silva