Darcs
Sign in to saveAlso known as Darcs Advanced Revision Control System
Darcs is a distributed version control system created by David Roundy. Key features include the ability to choose which changes to accept from other repositories, interaction with either other local (on-disk) repositories or remote repositories via SSH, HTTP, or email, and an unusually interactive interface. The developers also emphasize the use of advanced software tools for verifying correctness: the expressive type system of the functional programming language Haskell enforces some properties, and randomized testing via QuickCheck verifies many others. The name is a recursive acronym for Da
Key facts
- Software.logo
- Darcs-logo.png
- Software.logo alt
- darcs logo
- Software.name
- Darcs
- Software.author
- David Roundy
- Software.developer
- Guillaume Hoffmann, et al.
- Software.operating_system
- Unix, Linux, BSD, Apple macOS, MS Windows
- Software.genre
- Version control
- Software.license
- GPL-2.0-or-later
via Wikipedia infobox
Wikidata facts
- Official website
- darcs.net
Show 4 more facts
- software version identifier
- 2.18.5
- source code repository URL
- hub.darcs.net/darcs/darcs-reviewed
- inception
- 2003-03-03
- Commons category
- Darcs
Sources (7)
via Wikidata · CC0
~4 min read
Article
6 sectionsContents
- Model
- History
- Shortcomings
- See also
- References
- External links
Darcs is a distributed version control system created by David Roundy. Key features include the ability to choose which changes to accept from other repositories, interaction with either other local (on-disk) repositories or remote repositories via SSH, HTTP, or email, and an unusually interactive interface. The developers also emphasize the use of advanced software tools for verifying correctness: the expressive type system of the functional programming language Haskell enforces some properties, and randomized testing via QuickCheck verifies many others. The name is a recursive acronym for Darcs Advanced Revision Control System.
==Model== Darcs treats patches as first-class citizens. For the user, a repository can be seen as a set of patches, where each patch is not necessarily ordered with respect to other patches, i.e. the set of patches is only a partially ordered set. In many cases patches can be independently transmitted between various repositories.