<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - New Account Request" href="https://bugs.freedesktop.org/show_bug.cgi?id=90457#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - New Account Request" href="https://bugs.freedesktop.org/show_bug.cgi?id=90457">bug 90457</a> from <a class="email" href="mailto:cworth@cworth.org" title="Carl Worth <cworth@cworth.org>"> Carl Worth</a> <pre>(In reply to Brian Paul from <a href="show_bug.cgi?id=90457#c3">comment #3</a>) > Normally we don't give git privileges until after the individual has some > history of submitting some good patches. Right. > Carl, is Nanley is a coworker of your's at Intel? Yes. I fully expect Nanley to participate initially solely by submitting patches to the list. And, as in the normal course, he won't be pushing directly to git until he has established the history of submitting some good patches. At this point, we are really just creating a freedesktop account so that he would have a convenient place to publish git branches for code that he has developed. And for my convenience, (of just messing with the freedesktop account system once), I added his account to the mesa group. My expectation is that the result will be equivalent, (he won't be pushing until establishing the good history first). But if you would be more comfortable, I could go back in and change the account settings until he's actually demonstrated that. -Carl</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>