| Summary: | New Account Request | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Nanley Chery <nanleychery> |
| Component: | Other | Assignee: | mesa-dev |
| Status: | RESOLVED FIXED | QA Contact: | mesa-dev |
| Severity: | normal | ||
| Priority: | medium | CC: | cworth |
| Version: | git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
Public SSH key
Public PGP Key |
||
|
Description
Nanley Chery
2015-05-14 21:54:58 UTC
Created attachment 115785 [details]
Public PGP Key
Account added. Have fun, Nanley! Normally we don't give git privileges until after the individual has some history of submitting some good patches. Carl, is Nanley is a coworker of your's at Intel? (In reply to Brian Paul from comment #3) > 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 (In reply to Carl Worth from comment #4) > (In reply to Brian Paul from comment #3) > > 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. You can leave the account as-is. Just wanted to check. Thanks for the info, Carl. |
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.