Closed Bug 292198 Opened 20 years ago Closed 20 years ago

l10n CVS account request for Martin Creutziger

Categories

(mozilla.org :: Repository Account Requests, task)

task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: MMx, Assigned: marcia)

References

Details

(Whiteboard: voucher,ssh-key,form)

As we (MLP-staff) agreed in our last meeting, every member of MLP-staff should have CVS write access to the /l10n tree. Most are localizers themselfes, so they already have one. Others are peers to localizers. So I am requesting this account as member of MLP-staff and peer of the Firefox "de" locale, so as peer of Abdulkadir Topal. I already sent in a CVS form for the website CVS, see https://bugzilla.mozilla.org/show_bug.cgi?id=262971. There I also attached my SSH2-key. Should I reattach it here? Please tell me if you need anything else. Thanks.
... and I vouch.
Whiteboard: voucher,ssh-key,form
One detail I forgot: please use my email-adress "mmx_moz (at) c-comm.de" as account name, just as for the web-CVS account. I like to keep bugspam separate from everything else. ;-)
(In reply to comment #0) > I already sent in a CVS form for the website CVS, see > https://bugzilla.mozilla.org/show_bug.cgi?id=262971. There I also attached my > SSH2-key. Should I reattach it here? No need to reattach the key or resend the CVS form, marcia/admins should have them. And _please_ don't use bug URLs in bug comments but use just "bug 262971" as that gets linked as well and even gets the bug desc as title.
Yep, got your key off the other bug. (which actually that bug didn't need it :) your account has been given access to the l10n repo. This one *does* require SSH to access. Your CVSROOT should be mmx_moz%c-comm.de@cvs.mozilla.org:/l10n Don't forget to set the CVS_RSH evironment variable to 'ssh' first.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Account works fine. This is the quickest CVS-account creation I have seen so far! Thanks a lot! :)
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.