Hi Mike
At 08:43 30/08/02 -0700, Mike Noyes wrote:
On Fri, 2002-08-30 at 08:18, Julian Church wrote:
I got a
bit confused with editing the log file, so didn't put anything at all, and
I don't know what to do to control the version numbers either - the CVS
says the file is at 1.1 but I
On Mon, 2002-09-02 at 03:55, Julian Church wrote:
At 08:43 30/08/02 -0700, Mike Noyes wrote:
Log messages are important to let other project members know what you
did with your modification/addition. You can see examples of this in our
cvs-commits list archive.
Everyone,
I propose the creation of a config tree in our CVS src tree. All of the
components necessary for this project can be placed there, and write
access granted to team members. The structure of the config tree is left
to the team members discretion.
Example:
leaf/src/config +
Hi All
I'm about to start work converting another document to Docbook XML. I
think I'm moving onto the install guides for the different distributions
that are in the doc/guide part of the cvs tree.
My initial instinct was to start with the most recently released
distribution, and work back,
On Mon, 2002-09-02 at 10:13, Jacques Nilo wrote:
Hi Julian and list
FYI the Bering documentation (users and install guides) and my package
doc are available in XML from
http://leaf.sf.net/devel/jnilo/xml
I will move them to CVS when I will have some time.
Jacques,
I just did this for you.
Hi,
some remarks about using forth:
- certainly forth is missing all that nice pattern matching
like awk or perl, all this has to be coded.
- I assume that even arrays are not available in forth
- because forth uses very unusual semantics (reverse
polish notation) it is not easy to
