File: HACKING

package info (click to toggle)
peacock 0.4-5
  • links: PTS
  • area: main
  • in suites: woody
  • size: 1,340 kB
  • ctags: 649
  • sloc: ansic: 6,341; sh: 478; makefile: 309; sed: 93
file content (22 lines) | stat: -rw-r--r-- 924 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
Hacking on Peacock
------------------

Well, if you want to hack on Peacock, here are couple of things to be
taken into consideration.

	* Inform me about your plans, if you start hacking on Peacock.
	  Discuss your plans on the peacock-general@lists.sourceforge.net
	  first. What are you changing and basically kinda getting my
	  permission and keeping me informed. Send all patches to the
	  peacock-devel@lists.sourceforge.net mailing list before commiting
	  them to the CVS. And ofcourse get the latest source code from CVS,
	  before starting.
	* My coding style is mostly like Kernel Coding Style with traces
	  of GNU Coding Style, at places like header files. Even then,
	  just take a look at the code and figure it out.
	* Make sure you use Glib equivalent funtions of ANSI C functions
	  as far as possible. This make the program more portable.
	* Anything I missed here, check up with me.

Archit
March, 2000