summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--docs/FAQ11
1 files changed, 9 insertions, 2 deletions
diff --git a/docs/FAQ b/docs/FAQ
index e468f1a491..1fb6933559 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.
33 33
34Q8. Okay, so how do I submit a patch? 34Q8. Okay, so how do I submit a patch?
35A8. Run: "diff -ub oldfile newfile > patchfile" against the file(s) you have 35A8. Run: "diff -ub oldfile newfile > patchfile" against the file(s) you have
36 changed. Then mail the output to the rockbox mailing list and 36 changed. Then submit the patch to the project via Sourceforge's patch
37 we will take it under consideration. Please remember that all 37 tracker. See: http://sourceforge.net/tracker/?group_id=44306&atid=439120
38 Your patch will be taken under consideration. Please remember that all
38 submissions are not automatically accepted. This is nothing personal. 39 submissions are not automatically accepted. This is nothing personal.
39 40
40 Preferrably, run the diff against the current cvs code: 41 Preferrably, run the diff against the current cvs code:
41 cvs diff -ub > patchfile 42 cvs diff -ub > patchfile
42 43
44 One last note. We would appreciate it if *all* patches, files and fixes
45 that are meant for inclusion in the sources would be posted to the patch
46 tracker. Patches sent to the mailing list are quickly lost in the
47 traffic of the list itself. (And looking back in the archives for
48 missed patches quickly becomes a nightmare.)
49
43Q9. I want to join the development team, but don't have a SourceForge account, 50Q9. I want to join the development team, but don't have a SourceForge account,
44 what should I do? 51 what should I do?
45A9. You don't need a SourceForge account to help developing Rockbox. Just 52A9. You don't need a SourceForge account to help developing Rockbox. Just