Bug 105843 - Account request Wladimir van der Laan
Summary: Account request Wladimir van der Laan
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/etnaviv (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: fd.o Admin Massive
QA Contact: Etnaviv Developers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-02 09:43 UTC by Wladimir
Modified: 2018-04-02 18:52 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
SSH key (123 bytes, text/plain)
2018-04-02 09:43 UTC, Wladimir 		Details
PGP key (31.64 KB, text/plain)
2018-04-02 09:44 UTC, Wladimir 		Details
View All

Description Wladimir 2018-04-02 09:43:43 UTC 
Created attachment 138486 [details]
SSH key

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

I'd like to request an account for mesa.

real name: Wladimir van der Laan
email address: laanwj@gmail.com
preferred account name: laanwj
GPG fingerprint: 71A3 B167 3540 5025 D447  E8F2 7481 0B01 2346 C9A6 (pubkey attached)
SSH key fingerprint: SHA256:7Fo1QqW6p21tyrTYC3is1JmYxwk42OvhZkCiGf5kvZE (pubkey attached)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCgAGBQJawfr7AAoJEB5K7WKYbNJdmesH/1rZ3IL+fHBfJYfB+LS+Owfq
Yi3A45B4ZgN7a+BoVnnOTtHYHe+VbePnDS0P6OF779Hb/fEgr2i2AHim49p5DwJC
9F+VZYnDl2kDbIMHyZy5XqUNV3MOGhiVDGdW//dZhYalEPya5XeUeFOGiQ4X9rBN
r2V0CEJTpuJ97dtdMybpyALIjmeDRUT3oqfSLQ2FJ8b/g2CApSB7Na6kNSvebQp0
DAsxkXE1XreOgksQYQZYYIDx7QB+brKzJmHE5IAWwGxTHvK54c5H53EJQGuhf9Tq
XcuPDiihGhaBQdWxNODYrKDaLDFl6CA2/l8iMHXrJYBHvqfi6BbpVm/xUPip8uk=
=ywg8
-----END PGP SIGNATURE-----
Comment 1 Wladimir 2018-04-02 09:44:16 UTC 
Created attachment 138487 [details]
PGP key
Comment 2 Rob Clark 2018-04-02 11:39:24 UTC 
ack
Comment 3 Christian Gmeiner 2018-04-02 11:52:55 UTC 
+1
Comment 4 Daniel Stone 2018-04-02 18:52:32 UTC 
Done now; the account should be active in ~10 minutes. You'll be able to use ssh://git.freedesktop.org/git/mesa/mesa as a remote.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.