Skip to main content.

Brainstorming for a Version Control System for use with the Linux Kernel, U-Boot etc.

Monotone:

CON
importing the U-Boot CVS repository using the cvs_import command is slow (32 minutes)
CON
initial import using tailor fails

Darcs:

CON
Quote: "Darcs is not intended to maintain a history of versions, although it is possible to kludge together such a revision history, either by making each new patch dependent on all previous patches, or by tagging regularly."
This might result in QA issues, especially when some sort of certification is needed.
PRO
[Zachary P. Landau, 26 May 2005]:
excellent for cherry picking merges
CON
[Zachary P. Landau, 26 May 2005]:
speed issues ... especially the case with large trees (like the Linux kernel)
CON
cvs2darcs does not work - importing the U-Boot CVS repository results in an empty Darcs repository; not really critical as importing the CVS tree using tailor works just fine and pretty fast (1 minute 12 seconds)
CON
written in Haskell; non-trivial to build completely from sources only; no local know-how in case of problems or if extensions needed/wanted

-- WolfgangDenk - 30 May 2005