We have signed Google Corporate CLA so we need to update `AUTHORS` to replace individual entries to `*.brave.com`.
The instruction tells about adding entries, but not about updating them.`Please include this as part of your first patch and not as a separate standalone patch`.
If it's against the rules I can connect it to my other CL.
Also, is it possible to get dry run (CQ +1) access for *.brave.com accounts?
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
We have signed Google Corporate CLA so we need to update `AUTHORS` to replace individual entries to `*.brave.com`.
The instruction tells about adding entries, but not about updating them.`Please include this as part of your first patch and not as a separate standalone patch`.
If it's against the rules I can connect it to my other CL.Also, is it possible to get dry run (CQ +1) access for *.brave.com accounts?
I think updating this as a standalone is fine.
As for CQ+1 access, I am not sure how that would work. I'll ask around.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Daniel ChengWe have signed Google Corporate CLA so we need to update `AUTHORS` to replace individual entries to `*.brave.com`.
The instruction tells about adding entries, but not about updating them.`Please include this as part of your first patch and not as a separate standalone patch`.
If it's against the rules I can connect it to my other CL.Also, is it possible to get dry run (CQ +1) access for *.brave.com accounts?
I think updating this as a standalone is fine.
As for CQ+1 access, I am not sure how that would work. I'll ask around.
Thanks @dch...@chromium.org.
BTW, when I worked for Yandex (`*.yandex-team.ru`) we have CQ+1 by default, so I assume it isn't a special request.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Daniel ChengWe have signed Google Corporate CLA so we need to update `AUTHORS` to replace individual entries to `*.brave.com`.
The instruction tells about adding entries, but not about updating them.`Please include this as part of your first patch and not as a separate standalone patch`.
If it's against the rules I can connect it to my other CL.Also, is it possible to get dry run (CQ +1) access for *.brave.com accounts?
Mikhail AtuchinI think updating this as a standalone is fine.
As for CQ+1 access, I am not sure how that would work. I'll ask around.
Thanks @dch...@chromium.org.
BTW, when I worked for Yandex (`*.yandex-team.ru`) we have CQ+1 by default, so I assume it isn't a special request.
Hey Mikhail,
As far as I know, CQ+1 is granted on an account-by-account basis following the instructions here: https://www.chromium.org/getting-involved/become-a-committer/#try-job-access. I've nominated you for access (actually not even really nomination since you already had it - you just have a new e-mail address and affiliation, but your status in the chromium project comes with you). I've also asked whether *@brave.com is possible - perhaps I'm just unaware.
Thanks for continuing to contribute to Chromium!
Rick
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |