- User Since
- Aug 7 2013, 3:33 AM (314 w, 6 d)
Jan 6 2018
Oct 14 2016
Jul 12 2016
Jul 9 2016
@eadler, I was just able to resolve this on our installation by installing the php56w-mysqlnd package instead of php56w-mysql, which is what we had installed before.
Jun 5 2016
May 23 2016
That sounds like it might be what's going on. I apologize for not having better steps to reproduce; I'm working backward from example emails that folks are receiving, so it's been a bit of a guessing game as to how to make this happen.
Mar 7 2016
Awesome; thank you!
Mar 3 2016
Feb 19 2016
Jan 22 2016
Thanks, @epriestley (and sorry for getting back to you so late)! You're totally right that this is because I didn't actually update the revision.
Jan 20 2016
Jan 9 2016
Dec 9 2015
Nov 10 2015
Nov 9 2015
Excellent; that's good to know. Thanks!
Are these updates legitimately accidental? Can you explain how users are accidentally making updates to others' revisions? I don't think we've seen this behavior on this install, or heard about it from other installs.
Nov 6 2015
Thank you—that makes total sense. I'll track any feedback I hear from folks but will hold off on sending it your way until an appropriate feedback window opens up.
Nov 4 2015
Nov 2 2015
Cool; that makes total sense. Thanks again!
Oct 29 2015
This works great now; thank you very much!
Oct 28 2015
This is working great now; thanks so much for the fast turnaround!
That makes total sense—deleting master seems like a really bad idea in that case.
Awesome; D14357 does seem to fix this. Thanks! (Also, the new help documentation for arc land looks great.)
Oct 25 2015
Oct 23 2015
Oct 14 2015
Oct 13 2015
A nice middle ground would be if I could specify to show some branches by default—for example, just autoclose branches—and to have others hidden unless specifically requested.
Oct 10 2015
I think you're right; the best way forward for us to is to get more powerful filtering rules on the server side. In the meantime, your suggestion for using a mailing list or separate teams seems like a reasonable workaround. Thanks!
Oct 9 2015
(Cool—that seems very reasonable.)
It seems perfectly reasonably to tackle the specialty-workflow problem via T5055, rather than blowing up the number of Arcanist flags. And, as you suggest, I think T9537 will largely eliminate my desire for this, since it will allow me to name my local feature branches whatever I want, and I'll only have to type the long remote branch name at feature branch creation time.
Thanks, as always, for your prompt and thoughtful responses!
Oct 8 2015
I think you can create a "Mailing List" user and add them to the project to accomplish this. This is in addition to other mail delivery.
Thanks! It looks like the message delivery was voided because of my preference not to receive mail from Differential:
Hrm; I added a Herald rule that would email me if I'm in the list of reviewers, and changed all of the Differential Revision notification preferences to "Notify", but I didn't get an email when I changed a revision where I was a direct reviewer. (I verified that the Herald rule matched the revision in question using the test console.)
Thanks for the quick reply, @chad! If I understand it correctly, it sounds like you're right—T5791 is a superset of this request. Being able to write a Herald rule that drops outbound mail when I'm a project reviewer but allows it when I'm a direct reviewer would pretty much cover my use case.
Oct 6 2015
Oct 3 2015
Aug 26 2015
Thank you very much! I've updated to HEAD and everything seems to be running smoothly now.