Bug 44686 - Request for commit access
Summary: Request for commit access
Status: RESOLVED FIXED
Alias: None
Product: freedesktop.org
Classification: Unclassified
Component: New Accounts (show other bugs)
Version: unspecified
Hardware: Other All
: medium minor
Assignee: fd.o Admin Massive
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-11 09:21 UTC by Uli Schlachter
Modified: 2012-02-09 13:53 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Uli Schlachter 2012-01-11 09:21:39 UTC
Hi,

JD just told me to open this. :-)

I'd like to get commit access to the xcb git repos. No new GPG or SSH key needed, so the stuff from bug #32730 should be enough. Account name is "psychon".

Thanks
Comment 1 Julien Danjou 2012-01-11 09:27:02 UTC
Please give access to Uli.
Comment 2 Tollef Fog Heen 2012-02-09 13:10:30 UTC
I've now added you to the xorg group, which should grant access to the xcb repos.
Comment 3 Uli Schlachter 2012-02-09 13:27:12 UTC
Sorry for re-opening, but there really is a distinct "xcb" group (alanc from the #xcb IRC channel confirmed this).

Oh and "ls -l" says the repo is owned by the "xcb" group.

Also:

Counting objects: 7, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 650 bytes, done.
Total 4 (delta 3), reused 0 (delta 0)
error: unable to create temporary sha1 filename ./objects/a0: File exists

fatal: failed to write object
error: unpack failed: unpacker exited with error code
To ssh://psychon@git.freedesktop.org/git/xcb/libxcb
 ! [remote rejected] master -> master (n/a (unpacker error))
error: failed to push some refs to 'ssh://psychon@git.freedesktop.org/git/xcb/libxcb'
Comment 4 Tollef Fog Heen 2012-02-09 13:53:09 UTC
Yes, I discovered the xcb group a little bit after and moved you there.  Just be patient, user/groups are only updated every 20 minutes, so it should be ok any minute now.


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.