Welcome to OpenDEN
Custom Search
Version Control
Version control systems keep track of multiple versions of a source file. They provide a more powerful alternative to keeping backup files. From : www.nongnu.org/emacsdoc-fr/manuel/glossary.html
Management of changes or revisions to a specific baseline software module or application. Software version control provides a mechanism to control changes and to return to any previous revision of the application or module.
From : www.atlab.com/LIMS/glossaryp-t.html
FastCST
The three main features of FastCST are simply:
Fast as hell and simple to use. FastCST tries to make it as easy as possible to keep revisions of your stuff, share them with others, and with a minimum of hassle.
An extensible platform. FastCST supports a simple method of making your own commands in Ruby that involves nothing more than dropping them in the right directory.
A modern system that uses changesets over file revisions and distributed operation rather than centralized control. As long as you have an e-mail account you can use FastCST. For larger distribution you only need an FTP server and/or an HTTP server or use the built in serve command to serve your stuff up directly. All changesets are universally unique and have tons of meta-data so you can reject anything you dont before you try it. Merging is done by comparing a merged changeset against the current directory contents, rather than trying to merge it with another changeset.
Fast as hell and simple to use. FastCST tries to make it as easy as possible to keep revisions of your stuff, share them with others, and with a minimum of hassle.
An extensible platform. FastCST supports a simple method of making your own commands in Ruby that involves nothing more than dropping them in the right directory.
A modern system that uses changesets over file revisions and distributed operation rather than centralized control. As long as you have an e-mail account you can use FastCST. For larger distribution you only need an FTP server and/or an HTTP server or use the built in serve command to serve your stuff up directly. All changesets are universally unique and have tons of meta-data so you can reject anything you dont before you try it. Merging is done by comparing a merged changeset against the current directory contents, rather than trying to merge it with another changeset.
Loading .....
Recently Viewed Categories
Recently Viewed Products
