summaryrefslogtreecommitdiff
path: root/docs/FAQ
diff options
context:
space:
mode:
Diffstat (limited to 'docs/FAQ')
-rw-r--r--docs/FAQ11
1 files changed, 9 insertions, 2 deletions
diff --git a/docs/FAQ b/docs/FAQ
index e468f1a..1fb6933 100644
--- a/docs/FAQ
+++ b/docs/FAQ
@@ -33,13 +33,20 @@ A7. Start by reading up on the information about the jukeboxes on our web page.
Q8. Okay, so how do I submit a patch?
A8. Run: "diff -ub oldfile newfile > patchfile" against the file(s) you have
- changed. Then mail the output to the rockbox mailing list and
- we will take it under consideration. Please remember that all
+ changed. Then submit the patch to the project via Sourceforge's patch
+ tracker. See: http://sourceforge.net/tracker/?group_id=44306&atid=439120
+ Your patch will be taken under consideration. Please remember that all
submissions are not automatically accepted. This is nothing personal.
Preferrably, run the diff against the current cvs code:
cvs diff -ub > patchfile
+ One last note. We would appreciate it if *all* patches, files and fixes
+ that are meant for inclusion in the sources would be posted to the patch
+ tracker. Patches sent to the mailing list are quickly lost in the
+ traffic of the list itself. (And looking back in the archives for
+ missed patches quickly becomes a nightmare.)
+
Q9. I want to join the development team, but don't have a SourceForge account,
what should I do?
A9. You don't need a SourceForge account to help developing Rockbox. Just