зеркало из https://github.com/mozilla/gecko-dev.git
de38199aa2
Names changed from ReadMe* to README* and I also upper-cased the remainder bug 240082 |
||
---|---|---|
.. | ||
src | ||
.cvsignore | ||
ChangeLog | ||
Contact | ||
Goals | ||
Install | ||
Makefile.in | ||
Overview | ||
Policies | ||
README | ||
README.LOUNGE | ||
README.NETSCAPE_PROCESS | ||
README.TESTING_IDEAS | ||
ReleaseNotes | ||
Todo | ||
configure | ||
tinderbox.html | ||
tinderbox2-local-conf.spec | ||
tinderbox2.spec |
README
Directory Files --------------- Contact Information for getting in touch with the tinderbox author and maintainers ChangeLog A list of the changes that have been made to the source by date ReleaseNotes A list of changes that have been made since the last release Overview An overview of the Tinderbox2 system Policies Local policies you will need to define and understand before you can install Tinderbox2 Install Instructions on how to install Tinderbox2 at your location Todo A list of planned enhancements for the future and discussions of things which were included in Tinderbox1 but do not fit in the current architecture. Goals What were the goals for the the system and how does it differ from Tinderbox1 configure A program to scan your environment and create the Makefile Makefile A makefile to construct and install the system files *.spec Files which can be used to create Red Hat packages of the system for ease of installation and management. ReadMe.Netscape.Process A discussion of how the Netscape project uses this software. This will give you some ideas on how to use it on your project. ReadMe.Testing.Ideas Some ideas for additional things to test in your software. Tinderbox Documentation ----------------------- *) Every directory has a ReadMe file which tells about all the files in that directory. *) Every executable can be run with --help so that you can see what the program does and what its arguments are. If you have trouble running the file just look at the file in a text editor and find the string "usage". *) The top of every file (both code and configuration) has a short explanation of what this file does. *) The code has lots of documentation so you can read the code if you need more details about how something works.