1How to write code for FakeBO?
2-----------------------------
3
4If you wonder how do we like to code, It's hard to say. We have different
5opinions. Most of them are the same as Linus', so have a look at
6/usr/src/linux/Documentation/CodingStyle
7
8For inpatient:
9
10Please indent your sources with "indent -kr -i8"
11Send diffs in -u format
12Write changes interested for user in NEWS
13Developers will use ChangeLog to track changes
14	(which is created from time to time from CVS rcs)
15
16Please, use CVS! It's a great way to develop.
17
18CVSROOT=:pserver:anonymous@cvs.linux.hr:/cvsroot
19cvs login	(no password, just enter!)
20cvs checkout fakebo
21
22To get write access to CVS tree write to: <dpavlin@linux.hr>
23
24You will need latest-and-greatest tools after you do a checkout from
25CVS tree:
26
27automake (GNU automake) 1.4
28	(if you have 1.4a or higher, you can uncomment dist-bzip2)
29autoconf version 2.13
30
31If you have them, you can use autogen.sh to rebuild files which are needed
32and normal ./configure ; make to build FakeBO.
33
34You might want to subscribe to FakeBO developers mailing list by sending
35an e-mail to: fakebo-subscribe@linux.hr.
36