Skip to content
Hallway
0:00 / 0:00

#darcs#camp#patchtheory

Why do we continue to develop camp?

Ian Lynagh

9.5K subscribers • 1 video on Hallway

YouTube
  • Recommended by 2 people: 1 on Lobsters and 1 in engineering communities.
  • Presented by Ian Lynagh
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

21K views17 years ago2 recommendations

Tools and practiceSoftware designGit and version controlDesign patterns

Ian Lynagh explains why patch-centric version control systems like Camp and Darcs offer advantages over file-centric systems like Git.

In this video I explain what it is about camp and darcs that we believe makes them stand out from other version control systems.

Why it's here

2 people recommend this

What people say. Recommended as a clear explanation of patch-centric versus file-centric version control systems.

u/jshhollandin r/haskell • Recommends

On “darcs 2.10 is here! rebase; import/export to git; minimal patch bundles; pull --reorder; optimizations”

The fundamental object in darcs is the patch. The fundamental object in git/hg is the file. This makes it much easier to send individual changes without faffing around with dozens of different branches; you just push the ones you want. See this (rather old) video (for a fork of darcs, but the main idea is patch-centric vs file-centric) for a slightly more detailed explanation.
8View on Reddit

geocaron Lobsters • Recommends

Patch theory for dvcs. Also: Why do we continue to develop camp?
3View on Lobsters

u/kxrain r/haskell • Mentions

On “Darcs 2.14.0 released”

This is great! I'd love to see a CMS use Darcs as a backend for page revision history I remember that Camp \(link to this video\) was being worked on to form the basis of Darcs 3. What ever happened to that work?
9View on Reddit