darcs

(But of course, there were some; darcs and ghc for example.) The same is not true of Lisp.

We (Haskell community) were using dvcs through darcs for about 2 years prior to that.

Various algebras can be super-helpful, for example the patch-commutation algebra in the Darcs version control system, and the relational algebra underlying SQL.

Yes, Darcs predates Git by a few years and was used by GHC, XMonad, Happstack, and several other well-known Haskell projects.

It uses darcs and there's talk of a git mirror.

You can use BugsEverywhere with git, mercurial, bzr, darcs...

I wrote a Masters thesis about distributed issue tracking using darcs' patch theory[0].

I find centralized ones annoying; hopefully we've got Darcs & Git, both awesome.

Its just that usability-wise Darcs wins hands down.

Same thing with git compared to darcs/bzr/svn.

Has darcs just disappeared off the radar?

I converted a darcs repo to git and then used rebase to separate the huge mass of commits in the dev repo into their own branches.

"Darcs is the standard revision control system of the Haskell community." Hmm, was that the case in 2005?

> "To replicate and check methodology, `darcs clone...`".

"To replicate and check methodology, `darcs clone...`".

Darcs has "record", which is like "add -p" except it also commits at the same time, and back when I was using it, I remember hating the fact that it required that everything had to be recorded in one go.

Git, Mercurial, Darcs, Monotone, and Baazar all have a built-in bisect and for svn there are well used external scripts (like svn-bisect).