This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
documentation
- From: Bob Koninckx <bob dot koninckx at mech dot kuleuven dot ac dot be>
- To: ecos-discuss at sources dot redhat dot com
- Date: 12 Nov 2002 09:23:38 +0100
- Subject: [ECOS] documentation
Hi,
I have been working / improving on the mpc555 port this WE (mainly
further testing and improved serial debugging support, ctrl-c now
works). I was thinking of writing _some_ (certainly not too much, not
really something I like to do) documentation before submitting a patch.
Any pointers on the subject could be convenient (maybe I overlooked
something on the web). In particular
* How to generate the documentation from the source tree ?
* How is the documentation organized
* What belongs in which files ?
* Any conventions to follow ?
Thanks,
Bob
PS. Which cvs command generates a patch file in the format you guys
like? Do I run it in the root of the source tree or better generate
patches for those subsystems i changed?
--
----------------------------------------------------------------------
ir. Bob Koninckx
Katholieke Universiteit Leuven
Division Production Engineering, tel. +32 16 322535
Machine Design and Automation fax. +32 16 322987
Celestijnenlaan 300B bob.koninckx@mech.kuleuven.ac.be
B-3001 Leuven Belgium http://www.mech.kuleuven.ac.be/pma
----------------------------------------------------------------------
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss