Free content and version control

Free content and version control

Cherrypicking per se -- i.e., taking some changes from another version and applying them to your version -- is pretty easy. (I mean, these are just text files, and diff/patch can handle those well enough for most purposes, though you can also do somewhat better with real merge tech.) Where darcs runs into trouble, and where there are unsolved problems, is when you want later merges to be smart about respecting those past cherrypicks. But since they don't want to re-merge the two forks anyway, that doesn't matter. I don't see why you couldn't perfectly well import future edits from wikipedia into a "possible changes to review and click on the ones that you want to apply" interface.

(Some of us have made a similar argument about cherrypicking for software too, since the most important use cases are things like cherrypicking to stable branches that are never going to be merged back either.)