-= libcoaster Hacking procedures =-
This document describes what files and procedures are to be used when hacking on libcoaster's source.

** Patch & CVS procedures **
When using either CVS or making a patch, please update the Changelog with,

YYYY-MM-DD My Name <my@email.org>

	* /path/of/file.c: Changed item

For example a typical entry looks like.

2003-08-15 Sean Harshbarger <harshy@dersoldat.org>

	* TODO: updated list
	* /src/preferences.c: added header copyright
	* HACKING: started writing doc

If you are making a patch, please use the -u flag with diff. I prefer that all patches be made against cvs like:

cvs diff -u > patch.diff

Also please make all patches against the root coaster dir.

All patches are to be sent to me for approval. Anyone with cvs write access can feel free to commit minor changes without permission. When making a big revision, I would prefer you clear it with me beforehand.

** Coding Style **
When writing code, please use 8-space tabs. Opening curley braces should reside on the same line as its function/control. Closing curly braces should be on a new line by itself. Here is an example:

	for (!disk) {
		g_print ("Disc is not in use\n");
		gtk_main_quit ();
	}

Here is a typical one liner:

	for (!disk) g_print (Disc not in use\n");

Functions are like the following:

void
here_is_a_funtion (my *args)
{
	my_line = of_code;
}

Use only one line space between lines and try to block together same types of lines like paragraphs. Use 2 spaces between functions and prototype everything.
