Participating to PicForth development
Samuel Tardieu <[email protected]> 09 Nov 2004 15:49:11 +0100
| Newsgroups | gmane.comp.lang.forth.picforth |
|---|---|
| Organization | Avian Carrier & Friends |
| Message-ID | <[email protected]> |
In the past, I have had several requests from people who wanted to participate to PicForth development. To ease it, I have exported my Darcs (see http://www.darcs.net/) repositories of PicForth, representing the stable (picforth-1) and gforth 0.5.0 compatibility (picforth-0) branch. Darcs is very simple to use, probably even simpler than CVS. In Darcs, the working directory is a repository all by itself. It means that once you get the development version by using % darcs get http://www.rfc1149.net/download/picforth-repository/picforth-1 you get a picforth-1 repository in which you can make changes. For example, the following operations are immediately available in this directory: % darcs pull [pull new changes from my repository to yours] % darcs changes [gives you a list of changes present in your repository] % darcs add ... [add new files in the repository] % darcs record [record new changes locally after having run regression tests] % darcs send [send selected changes to [email protected] for inclusion in the officiel PicForth repository] Sending me changes through darcs guarantees a better response time. If you choose to, you can of course publish your own repository and let other people access your changes and derive theirs from yours. You can look at the "mirror" target in the development version of the Makefile to see how I mirror my changes from my local repository to the publicly visible one. Sam -- Samuel Tardieu -- [email protected] -- http://www.rfc1149.net/sam