From b0529e1604c1c2ee34c1d66485f3955d08838a03 Mon Sep 17 00:00:00 2001 From: joey Date: Tue, 23 Jan 2007 03:15:58 +0000 Subject: [PATCH] web commit by http://bmalee.eu/~bma/: Add my opinion on darcs. --- doc/about_rcs_backends.mdwn | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/about_rcs_backends.mdwn b/doc/about_rcs_backends.mdwn index d1454bdda..8d6c00f9f 100644 --- a/doc/about_rcs_backends.mdwn +++ b/doc/about_rcs_backends.mdwn @@ -103,6 +103,8 @@ by Ikiwiki. This approach might be applicable to other distributed VCSs as well, although they're not as oriented towards transmitting changes with standalone patch bundles (often by email) as darcs is. +> The mercurial plugin seems to just use one repo and edit it directly - is there some reason that's okay there but not for darcs? I agree with tuomov that having just the one repo would be preferable; the point of a dvcs is that there's no difference between one repo and another. I've got a darcs.pm based on mercurial.pm, that's almost usable... --bma + ## [[Git]] Regarding the Git support, Recai says: