Updated developer info

git-svn-id: svn://svn.rockbox.org/rockbox/trunk@1959 a1c6a512-1295-4272-9138-f99709370657
This commit is contained in:
Björn Stenberg 2002-08-23 20:49:12 +00:00
parent 3df58d30e1
commit 10fc53c75f

View file

@ -32,18 +32,23 @@ A7. Start by reading up on the information about the jukeboxes on our web page.
need and start writing. need and start writing.
Q8. Okay, so how do I submit a patch? Q8. Okay, so how do I submit a patch?
A8. Run: "diff -u oldfile newfile > patchfile" against the file(s) you have A8. Run: "diff -ub oldfile newfile > patchfile" against the file(s) you have
changed. Then mail the output to any member of the development team and changed. Then mail the output to the rockbox mailing list and
we will take it under consideration. (Please remember that all we will take it under consideration. Please remember that all
submissions are not automatically accepted, this is nothing personal.) submissions are not automatically accepted. This is nothing personal.
Of if you would like to run the diff against the current cvs code: Preferrably, run the diff against the current cvs code:
cvs diff -ub [file(s)] cvs diff -ub > patchfile
Q9. I want to join the development team, but don't have a SourceForge account, Q9. I want to join the development team, but don't have a SourceForge account,
what should I do? what should I do?
A9. Head on over to http://sourceforge.net/account/register.php and create an A9. You don't need a SourceForge account to help developing Rockbox. Just
account for yourself. submit patches to the mailing list as per the instructions above.
If your patches are consistently well-written and thus accepted, you may
ultimately be offered CVS commit access. If that should happen, you will
need to get a Sourceforge account:
http://sourceforge.net/account/register.php
Q10. Do you have a mailing list? Q10. Do you have a mailing list?
A10. Sure do! As a matter of fact, we have several of them for specific A10. Sure do! As a matter of fact, we have several of them for specific