Commit Access (Level 1) for Emanuel Hoogeveen

RESOLVED FIXED

Status

RESOLVED FIXED
6 years ago
5 years ago

People

(Reporter: ehoogeveen, Assigned: Usul)

Tracking

Details

Attachments

(1 attachment)

(Reporter)

Description

6 years ago
Created attachment 767247 [details]
Public key

I would hereby like to request level 1 commit access. I've attached my SSH public key, and will fill out the Committer's Agreement shortly.

Comment 1

6 years ago
I'll vouch for you. Leave a comment when you've sent off the form.
(Reporter)

Comment 2

6 years ago
Excellent! I've e-mailed the form to sarmitage@mozilla.com.

Also, I forgot to mention this in the first post: I would like to use emanuel.hoogeveen@gmail.com as my login name.
Flags: needinfo?(sarmitage)
I vouch for Emanuel as well (not that it's necessary, but hey, I said I would :)
I have received the form.
Flags: needinfo?(sarmitage)

Comment 5

6 years ago
Git 'er done.
Assignee: mozillamarcia.knous → server-ops
(Assignee)

Comment 6

5 years ago
LDAP account created. Bit sets for HG, email with password and instructions sent.
Assignee: server-ops → ludovic
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
(Reporter)

Comment 7

5 years ago
\o/ Thanks everyone!
You should do a test push to make sure it's working.  Do you know about http://trychooser.pub.build.mozilla.org/?  You need to use it to specify which platforms, builds and tests you want.  For a test push you could just do a single build on a single platform.
(Reporter)

Comment 9

5 years ago
I sent a particularly green revision of m-i to try:
https://tbpl.mozilla.org/?tree=Try&rev=0875d1b47b03

Just one platform, no tests. The line that says "f23f10c7969b Emanuel Hoogeveen – imported patch clang-warnings" has me puzzled - I have no patches in my queue other than the one I made for the try push! The build seems to have finished okay, at least.
Could you have committed that "imported patch clang-warnings" by accident?  Check |hg log|.
(Reporter)

Comment 11

5 years ago
Yeah, I must have done something wrong. I stripped the changeset from my tree, so it should be clean now (I hope).
You need to log in before you can comment on or make changes to this bug.