------- Comment #10 from manu at gcc dot gnu dot org 2007-01-17 19:12 ------- I am also new, my first patch was just a few months ago, so let me say that I understand your situation. On the other hand, I got patches committed, so also let me say that it is not as bad as you may think.
The secret handshake is quite simple actually: 1) Have a copyright assignment: http://gcc.gnu.org/contribute.html#legal 2) Post patches to [EMAIL PROTECTED] (you can also add them to the patch queue http://www.dberlin.org/patchdirections.html but posting to gcc-patches is essential, bugzilla attachments are not considered serious proposals). 3) Add testcases to the patch and bootstrap and regression test for a recent revision, and say that you have done so. Add a Changelog to your mail (but not to the patch). More info at http://gcc.gnu.org/contribute.html 4) Wait, wait, wait, make a comment about your patch pending review (if you follow the list, you will see that people do this very often), then wait, wait and wait a bit more, perhaps make another comment and eventually your patch will be reviewed and surely you will have to make changes. In that case, goto 2. 5) Ask for someone to commit the patch for yourself or ask for write-after-approval rights. The wait-wait-wait thing may apply here again. Patience, you can have as many patches pending review as you wish, just ping them once every while. Easy, isn't it? I think the first step is to get subscribed to gcc-patches to check out how people submit and get reviewed patches. What are you waiting for? We look forward to have you on board! Cheers, Manuel. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16202
