Closed
Bug 659967
Opened 15 years ago
Closed 15 years ago
Please grant kev@mozilla.com write access to the build/partner-repacks repo
Categories
(mozilla.org :: Repository Account Requests, task)
mozilla.org
Repository Account Requests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: coop, Unassigned)
Details
I'm not sure if we have the fine-control to grant Kev access to just the partner-repacks repo within build. If not, we're OK with Kev having the broader access to build to facilitate his partner work.
Comment 1•15 years ago
|
||
There are no fine-grained controls on Hg, just the "levels" (1/2/3). I imagine build/partner-repacks falls under level 2.
Kev already has an SVN account, so this should just be a matter of enabling the Hg and relevant level bits.
Kev: you originally got your access before we updated the committer form, so you should probably sign a new form if you haven't done it already. http://www.mozilla.org/hacking/notification/
Assignee: mozillamarcia.knous → desktop-support
| Reporter | ||
Comment 2•15 years ago
|
||
(In reply to comment #1)
> Kev: you originally got your access before we updated the committer form, so
> you should probably sign a new form if you haven't done it already.
> http://www.mozilla.org/hacking/notification/
Kev: Any update here?
Comment 3•15 years ago
|
||
I missed the "sign the new form" comment. I'll do that, and will promise not to mess with anything outside repacks because, srsly, I don't want Gavin doing a TOnya Harding impression.
Comment 4•15 years ago
|
||
To be clear, this bug doesn't need to block on the new form. Server-ops should feel free to be doing the relevant bitflippery!
Comment 5•15 years ago
|
||
(In reply to comment #4)
> To be clear, this bug doesn't need to block on the new form. Server-ops
> should feel free to be doing the relevant bitflippery!
zandr/amy: I'm not sure who to ask in IT - any ETA on this?
Comment 6•15 years ago
|
||
HG level 2 access granted for kneedham@mozilla.com.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•