User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_4; th-th) AppleWebKit/525.18 (KHTML, like Gecko) Version/3.1.2 Safari/525.20.1 Build Identifier: SVN account request for Patipat Susumpow from Thai localisation team on Mozilla Products (Firefox, Thunderbird, Camino). Refer to Bug 443375, I'd sent the committer agreement to Mozilla both scanned and hard copy version. Reproducible: Always
Patipat, for the nth time, don't use firstname.lastname@example.org. I'll start dropping your requests on that account from now on. Moving over to CVS account requests, as that is what it is.
Status: UNCONFIRMED → NEW
Component: Account Request: SVN → Account Request: CVS
Ever confirmed: true
QA Contact: svn-acct-req → cvs-acct-req
(In reply to comment #2) > Patipat, for the nth time, don't use email@example.com. I'll start dropping your > requests on that account from now on. Moving over to CVS account requests, as > that is what it is. > sorry about that. just my thought that l10n@mozilla is not yours,
I think the process is the same as bug #450208. Then, I also vouch this request.
I have received Patipat's Committer's Agreement.
Doubling the voucher, Marcia, I think this is ready for IT.
Over to server-ops for account creation.
Assignee: marcia → server-ops
the bugs subject says its an l10n cvs request. The body mentions svn, we are now also using mercurial. Can someone list the accounts that need to be created.
Assignee: server-ops → aravind
(In reply to comment #9) > the bugs subject says its an l10n cvs request. The body mentions svn, we are > now also using mercurial. Can someone list the accounts that need to be > created. CVS and Hg
Attachment #332723 - Attachment mime type: application/octet-stream → text/plain
Your CVS account has been created. Your CVSROOT should be: firstname.lastname@example.org:/l10n Don't forget to set your CVS_RSH environment variable to 'ssh'. If you have any problems connecting, let me know. You have a l10n mercuiral account as well.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.