First version

git-svn-id: svn://svn.rockbox.org/rockbox/trunk@86 a1c6a512-1295-4272-9138-f99709370657

2 files changed, 40 insertions, 0 deletions

diff --git a/firmware/CONTRIBUTING b/firmware/CONTRIBUTING
new file mode 100644
index 0000000..b38409a
--- /dev/null
+++ b/firmware/CONTRIBUTING
@@ -0,0 +1,18 @@
+$Id$
+
+In order for the project to run as smoothly as possible, it's best if all
+contributors adhere to a few simple conventions:
+
+- Write all code in C. Sometimes assembly is faster, but C is always more
+  readable and maintainable.
+
+- Write C code. Don't redefine the language. No new types, no C++isms or
+  Javaisms.
+
+- Variables and function names should be all lower case.
+  Preprocessor symbols should be all uppercase.
+
+- Use the brace placement style of your choice, but indent your code with
+  four spaces. Don't use TAB characters, as that will mess up code display in
+  CVS, printing, and a zillion other places.
+
diff --git a/firmware/rockbox-mode.el b/firmware/rockbox-mode.el
new file mode 100644
index 0000000..5ede3b4
--- /dev/null
+++ b/firmware/rockbox-mode.el
@@ -0,0 +1,22 @@
+;;;; Emacs Lisp help for writing rockbox code. ;;;;
+;;;; $Id$
+
+;;; In C files, put something like this to load this file automatically:
+;;
+;;   /* -----------------------------------------------------------------
+;;    * local variables:
+;;    * eval: (load-file "../curl-mode.el")
+;;    * end:
+;;    */
+;;
+;; (note: make sure to get the path right in the argument to load-file).
+
+
+;;; The rockbox hacker's C conventions
+
+;;; we use intent-level 2
+(setq c-basic-offset 4)
+;;; never ever use tabs to indent!
+(setq indent-tabs-mode nil)
+;;; I like this, stolen from Subversion! ;-)
+(setq angry-mob-with-torches-and-pitchforks t)