Darcs is a distributed advanced revision control system written in Haskell. It is similar to Git, Mercurial and Bazaar. User will have own personnel repository and commits his changes to it. Later the changes are pushed to the centralized repository. Every repository is a branch and it provides support to integrate the changes between them. It provides support to send the changes by email. The fundamental difference is that Git, Mercurial and Bazaar maintains a chronological order in the changes of the repository. Darcs manipulates patches instead of chronological revisions, so darcs maintains a more fine-grained order on changes, that could be called patches dependencies.

Darcs is a distributed advanced revision control system written in Haskell. It is similar to Git, Mercurial and Bazaar. User will have own personnel repository and commits his changes to it. Later the changes are pushed to the centralized repository. Every repository is a branch and it provides support to integrate the changes between them. It provides support to send the changes by email.

Darcs - Distributed Revision Control in Haskell

Fossil is a distributed version control like Git and Mercurial. Fossil also supports distributed bug tracking and distributed wiki all in a single integrated package. It is simple, high-reliability, distributed software configuration management. Its feature include: 
 <UL>
	<LI>Bug Tracking And Wiki</LI>
	<LI>Web interface</LI>
	<LI>Autosync - avoids forking and merging</LI>
	<LI>Uses HTTP for all network communications, it works fine from behind restrictive firewalls</LI>
	<LI>CGI Enabled</LI>
	<LI>Fossil stores content in an SQLite database so that transactions are atomic even if interrupted by a power loss or system crash</LI>
 </UL>

Fossil is a distributed version control like Git and Mercurial. Fossil also supports distributed bug tracking and distributed wiki all in a single integrated package. It is simple, high-reliability, distributed software configuration management.

Fossil

Monotone is a free distributed version control system. It provides a simple, single-file transactional version store, with fully disconnected operation and an efficient peer-to-peer synchronization protocol. It understands history-sensitive merging, lightweight branches, integrated code review and 3rd party testing. It uses cryptographic version naming and client-side RSA certificates. It has good internationalization support. Its feature include: 
 <UL>
	<LI>Store multiple versions of files you are working on efficiently</LI>
	<LI>Transmit changes to files between you and your colleagues</LI>
	<LI>Merge changes you make with those your colleagues make</LI>
	<LI>Make notes about your opinion of the quality of versions of files</LI>
	<LI>Make decisions about using or ignoring versions, depending on the notes you receive from others</LI>
 </UL>

Monotone is a free distributed version control system. It provides a simple, single-file transactional version store, with fully disconnected operation and an efficient peer-to-peer synchronization protocol. It understands history-sensitive merging, lightweight branches, integrated code review and 3rd party testing. It uses cryptographic version naming and client-side RSA certificates.

Monotone

CVS is a version control system, an important component of Source Configuration Management (SCM). Using it, you can record the history of sources files, and documents. CVS is a production quality system in wide use around the world, including many free software projects. 
 <ul><li>It can run scripts which you can supply to log CVS operations or enforce 
 site-specific polices.</li><li> Client/server CVS enables developers scattered by geography or slowmodems to function as a single team. The version history is stored on
a single central server and the client machines have a copy of all the files that the developers are working on. Therefore, the network between the client and the server must be up to perform CVS operations
(such as checkins or updates) but need not be up to edit or manipulate the
current versions of the files. Clients can perform all the same
operations which are available locally.</li><li>In cases where several developers or teams want to each maintain
their own version of the files, because of geography and/or policy,
CVS's vendor branches can import a version from another team
(even if they don't use CVS), and then CVS can merge the changes from
the vendor branch with the latest files if that is what is desired. </li><li>
Unreserved checkouts, allowing more than one developer to work on
the same files at the same time.</li><li>CVS provides a flexible modules database that provides a symbolic mapping of names to components of a larger software distribution. It
applies names to collections of directories and files. A single
command can manipulate the entire collection. </li></ul>

CVS is a version control system, an important component of Source Configuration Management (SCM). Using it, you can record the history of sources files, and documents. CVS is a production quality system in wide use around the world, including many free software projects.

Discover open source projects across all platforms

Projects

Darcs - Distributed Revision Control in Haskell

Fossil

Monotone

CVS

TechStack

Tagcloud

Suggested keywords:

Projects

Darcs - Distributed Revision Control in Haskell

Fossil

Monotone

CVS

TechStack

Tagcloud