Page MenuHomePhabricator

llvmOrganization
ActivePublic

Watchers

  • This project does not have any watchers.
  • View All

Details

Description

For tracking llvm related bugs and such

Recent Activity

Jan 16 2019

epriestley closed T7477: Handle inbound email with phabricator address in the CC as Resolved by committing rPe3aa043a0272: Allow multiple mail receivers to react to an individual email.
Jan 16 2019, 8:28 PM · llvm, Restricted Project, Restricted Project, Mail

Jan 3 2019

epriestley added a revision to T7477: Handle inbound email with phabricator address in the CC: D19952: Allow multiple mail receivers to react to an individual email.
Jan 3 2019, 7:47 PM · llvm, Restricted Project, Restricted Project, Mail
epriestley claimed T7477: Handle inbound email with phabricator address in the CC.
Jan 3 2019, 6:49 PM · llvm, Restricted Project, Restricted Project, Mail
epriestley added a revision to T7477: Handle inbound email with phabricator address in the CC: D19950: Consolidate some application email receiver code in preparation for API changes.
Jan 3 2019, 5:56 PM · llvm, Restricted Project, Restricted Project, Mail
epriestley added a revision to T7477: Handle inbound email with phabricator address in the CC: D19949: Remove "metamta.insecure-auth-with-reply-to" Config option.
Jan 3 2019, 4:45 PM · llvm, Restricted Project, Restricted Project, Mail
epriestley added a revision to T7477: Handle inbound email with phabricator address in the CC: D19948: Extract some email address utility code from the receiver stack.
Jan 3 2019, 4:06 PM · llvm, Restricted Project, Restricted Project, Mail
epriestley added a revision to T7477: Handle inbound email with phabricator address in the CC: D19947: Drop empty inbound mail at the beginning of the receive workflow, not inside object handlers.
Jan 3 2019, 2:28 PM · llvm, Restricted Project, Restricted Project, Mail
klimek added a comment to T4926: When emails are sent to new people (or lists) they should contain the change description and patch.

For the record: I'd like us to get away from maintaining our own phab fork, and I agree that means probably migrating to a different system at some point.

Jan 3 2019, 11:18 AM · llvm, Mail, Differential

Jan 2 2019

chandlerc added a comment to T4926: When emails are sent to new people (or lists) they should contain the change description and patch.

FWIW, I think describing these as "non mainstream" and the entire description of these communities sounds to me ... somewhere between biased and pejorative. Makes it hard for me to keep engaging in the discussion.

Jan 2 2019, 9:17 PM · llvm, Mail, Differential
epriestley added a comment to T4926: When emails are sent to new people (or lists) they should contain the change description and patch.

Maybe worth a mention -- GHC is another somewhat-similar project and moving to GitLab (e.g., https://mail.haskell.org/pipermail/ghc-devs/2018-October/016425.html). It sounds like GitLab is currently better able to spend resources to support free users with relatively non-mainstream use cases than we are.

Jan 2 2019, 6:38 PM · llvm, Mail, Differential
emaste added a comment to T4926: When emails are sent to new people (or lists) they should contain the change description and patch.

For the record, yes, FreeBSD is quite similar and what @chandlerc wrote is very much applicable to our community as well.

Jan 2 2019, 6:37 PM · llvm, Mail, Differential
epriestley added a comment to T4926: When emails are sent to new people (or lists) they should contain the change description and patch.

I think a lot of this behavior may be fairly unique to the LLVM project, since we've never really received this general class of feedback from other installs (except, perhaps, FreeBSD, which I think is somewhat culturally similar).

Jan 2 2019, 6:23 PM · llvm, Mail, Differential
chandlerc added a comment to T4926: When emails are sent to new people (or lists) they should contain the change description and patch.

For the record, while the rationale can be flippantly described as "I don't like clicking things", I'd like to give it a serious description.

Jan 2 2019, 5:44 PM · llvm, Mail, Differential
epriestley closed T9012: Nag users who reply-all as Wontfix.

I'm generally very hesitant to "nag" users, and this conflicts with T7477 (which wants email to a group of users, including an application email address, to work). Of the two, I think T7477 is significantly more valuable. And, some day, many years from now, I'd theoretically like to make metamta.one-mail-per-recipient the only supported mode, which fixes this anyway.

Jan 2 2019, 5:11 PM · llvm, Mail, Restricted Project
epriestley moved T6162: Add an "Email and unread notification" option in user's Email Preferences from Backlog to Future on the Mail board.
Jan 2 2019, 5:05 PM · Notifications, llvm, Restricted Project, Mail
epriestley closed T4926: When emails are sent to new people (or lists) they should contain the change description and patch as Wontfix.

I don't plan to change this without a better understanding of what problem we're solving. New users can click the link in the email to review the discussion, summary, and patch.

Jan 2 2019, 5:00 PM · llvm, Mail, Differential
epriestley closed T1837: Implement correct send-as-user behavior. as Wontfix.

Not clear that "Sender" is worth pursuing, even if it does give us more flexibility around configuring the "From" header in some cases.

Jan 2 2019, 3:30 PM · llvm, Restricted Project, Mail
epriestley closed T1735: Improve implementation of "Re:" prefix by dropping it from messages which are unambiguously first-in-thread as Invalid.

This is years old and I have no idea how to reproduce it. (I use Mail with "Organize by Conversation" as my primary mail client, and have for about a decade.)

Jan 2 2019, 3:27 PM · llvm, Restricted Project, Mail
epriestley moved T7477: Handle inbound email with phabricator address in the CC from Future to Soon? on the Mail board.
Jan 2 2019, 3:19 PM · llvm, Restricted Project, Restricted Project, Mail

Feb 8 2018

epriestley moved T7477: Handle inbound email with phabricator address in the CC from Stamps/Failover to Future on the Mail board.
Feb 8 2018, 6:02 PM · llvm, Restricted Project, Restricted Project, Mail
epriestley added a comment to T7477: Handle inbound email with phabricator address in the CC.

The scope on T13053 didn't end up making it very far in this direction so I think this missed the boat for now.

Feb 8 2018, 6:02 PM · llvm, Restricted Project, Restricted Project, Mail
epriestley added a comment to T8363: Include reply action ("!action") hints in outbound email.

T11934 plans to add these commands everywhere. If they're available all over the place, it might be less necessary to add reminders.

Feb 8 2018, 6:00 PM · llvm, Restricted Project, Mail
epriestley moved T8363: Include reply action ("!action") hints in outbound email from Backlog to Future on the Mail board.
Feb 8 2018, 5:58 PM · llvm, Restricted Project, Mail
epriestley closed T6576: HTML bodies are not passed to all emails as Resolved by committing rPbae9f459ab7f: Pass HTML bodies to push email.
Feb 8 2018, 5:12 PM · llvm, Mail
epriestley added a comment to T6576: HTML bodies are not passed to all emails.

I've marked D19029 as resolving this since it fixes the last one of these that I'm aware of. HTML mail has been the default for a long time now so this presumably isn't really causing problems even if there are other cases.

Feb 8 2018, 5:08 PM · llvm, Mail
epriestley added a revision to T6576: HTML bodies are not passed to all emails: D19029: Pass HTML bodies to push email.
Feb 8 2018, 5:08 PM · llvm, Mail
epriestley moved T6576: HTML bodies are not passed to all emails from v3 to Stamps/Failover on the Mail board.
Feb 8 2018, 5:04 PM · llvm, Mail

Jan 27 2018

epriestley moved T7477: Handle inbound email with phabricator address in the CC from Backlog to Stamps/Failover on the Mail board.
Jan 27 2018, 9:57 PM · llvm, Restricted Project, Restricted Project, Mail
epriestley closed T11337: Mail v3 as Wontfix.

I'm rolling this forward into T13053.

Jan 27 2018, 9:53 PM · llvm, Mail

Jul 9 2017

chad removed the image for llvm.
Jul 9 2017, 7:37 PM
chad set the icon for llvm to Organization.
Jul 9 2017, 7:37 PM

Jun 23 2017

aklapper added a comment to T8363: Include reply action ("!action") hints in outbound email.

I think that these use to exist and were moved to a help document somewhere.

Jun 23 2017, 5:31 PM · llvm, Restricted Project, Mail

May 15 2017

alexmv added a comment to T7477: Handle inbound email with phabricator address in the CC.

Understood -- thanks for the clarification. One isn't always aware of how special-case one is. :)

May 15 2017, 4:14 PM · llvm, Restricted Project, Restricted Project, Mail
epriestley added a comment to T7477: Handle inbound email with phabricator address in the CC.

Many of the patches you've personally contributed in the past have bypassed the bulk of the requirements under the "Rise to Prominence" clause of Contributing Code, since you have a history with the project, are a member of Community, and have generally contributed very focused patches with clear context:

May 15 2017, 3:11 PM · llvm, Restricted Project, Restricted Project, Mail
alexmv added a comment to T7477: Handle inbound email with phabricator address in the CC.

Sorry, that seemed to be in response to "are you working on this?" A user has since provided a patch for the feature, which is the sort of thing which in the past you folks have generally been nice enough to review.

May 15 2017, 2:53 PM · llvm, Restricted Project, Restricted Project, Mail
epriestley added a comment to T7477: Handle inbound email with phabricator address in the CC.

Per above, see Planning. If that isn't clear, let me know how we could improve it.

May 15 2017, 2:48 PM · llvm, Restricted Project, Restricted Project, Mail
alexmv added a comment to T7477: Handle inbound email with phabricator address in the CC.

Phacility folks, do you have thoughts about the patch provided by @lyngvi above? Would be it be easier to review if submitted as a Diff?

May 15 2017, 2:45 PM · llvm, Restricted Project, Restricted Project, Mail

May 14 2017

chad added a comment to T9412: Annotate all the reasons that a user is included on the recipient list for mail.

Filed T12707 to follow up.

May 14 2017, 4:03 PM · llvm, Restricted Project, Mail
chad added a comment to T9412: Annotate all the reasons that a user is included on the recipient list for mail.

I don't expect watchers to be on profile, but we should provide a search for it in /projects/

May 14 2017, 3:54 PM · llvm, Restricted Project, Mail
aklapper added a comment to T9412: Annotate all the reasons that a user is included on the recipient list for mail.

Another anecdote explaining that the current situation is confusing:
As a user who has not been active in Phabricator for a while and as my interests in projects might have shifted, I am trying to find out why I receive email notifications about certain tasks and how to disable these specific notifications to reduce the amount of uninteresting mail. But:

  • My "Profile" user page does not list any "Projects".
  • The email headers do not tell me either why I received an email.

After some thinking I realized that the reason was that I was a watcher (but not a member) of an associated project tag of a task.
I'd expect my "Profile" user page to not only list "Projects" (actually means: Member) but also projects that I only watch. Currently I need to go to one of the tasks that I received an email about, click all associated projects, and go to the "Members and Watchers" page of each project to find out that I once added myself as a "watcher" and remove myself.
However, that might still not explain why I received a specific email: If I have "Settings > Email > Email Preferences > Maniphest Tasks > One of a task's subtasks changes status" enabled, I also need to check all subtasks' projects whether I watch one of them.

May 14 2017, 3:47 PM · llvm, Restricted Project, Mail

Apr 17 2017

epriestley edited projects for T6162: Add an "Email and unread notification" option in user's Email Preferences, added: Notifications; removed Aphlict.
Apr 17 2017, 12:08 PM · Notifications, llvm, Restricted Project, Mail

Feb 13 2017

epriestley closed T10105: Disabled account should disable all outbound mail as Wontfix.

Example: I disabled a bogus user when the "confirm your e-mail" MTA job was on its ~200th attempt. It's now at its ~240th attempt :)

Feb 13 2017, 6:42 PM · llvm, Restricted Project, Mail, Bug Report

Jan 5 2017

lyngvi added a comment to T7477: Handle inbound email with phabricator address in the CC.

Patch attached which addresses this - filter and object selection done on a new getToOrCCAddresses call. This patch is based off stable branch commit 58375fa9e6db4a389fd6029ee1ad14ddb0dc9e90.

Jan 5 2017, 4:30 PM · llvm, Restricted Project, Restricted Project, Mail

Dec 26 2016

epriestley added a comment to T1837: Implement correct send-as-user behavior..

Note that there is a Sender-related RCE in PHPMailer until Dec 2016, see T12046 for discussion.

Dec 26 2016, 4:37 PM · llvm, Restricted Project, Mail

Dec 5 2016

epriestley closed T11950: jkhkjhkjh as Invalid.
Dec 5 2016, 2:19 PM · llvm, Abuse
kobbygl added a project to T11950: jkhkjhkjh: llvm.
Dec 5 2016, 2:12 PM · llvm, Abuse

Sep 30 2016

eadler moved T4926: When emails are sent to new people (or lists) they should contain the change description and patch from Backlog to Nits on the llvm board.
Sep 30 2016, 7:08 AM · llvm, Mail, Differential
eadler moved T11337: Mail v3 from Backlog to Nits on the llvm board.
Sep 30 2016, 7:08 AM · llvm, Mail
eadler moved T5181: Parse in-line replies in email responses from Backlog to Important on the llvm board.
Sep 30 2016, 7:08 AM · llvm, Restricted Project, Mail
eadler moved T9412: Annotate all the reasons that a user is included on the recipient list for mail from Backlog to Nice To Have on the llvm board.
Sep 30 2016, 7:08 AM · llvm, Restricted Project, Mail