git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Hudec <bulb@ucw.cz>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Bu Bacoo <bubacoo@gmail.com>,
	git@vger.kernel.org
Subject: Re: Darcs
Date: Sun, 24 Jun 2007 23:19:52 +0200	[thread overview]
Message-ID: <20070624211952.GA3044@efreet.light.src> (raw)
In-Reply-To: <46a038f90706241345m4b5ecb80p9f4ec840993023e0@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2145 bytes --]

On Mon, Jun 25, 2007 at 08:45:57 +1200, Martin Langhoff wrote:
> On 6/25/07, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> >Ahh, a chance to flame! I will never back down from such a challenge!
> >
> >Darcs is .. umm .. ehh..
> >
> >"Academic".

> OTOH, and from the POV of someone closely following the SCM tools in
> the last few years (and using almost all of them), darcs was the first
> usable DSCM in the camp. I am not sure how much of its commandline
> user interface was borrowed from BK or elsewhere, but darcs was
> _easy_, where Arch was extremely hard to use.

Arch is not in fact distributed. One key feature that makes things
distributed is that object (revision in SCM) identity is independent of their
location (repository in SCM). And in Arch that is not true.

Revisions independent of repositories (and branches) is what makes the ad-hoc
branching, that makes git (and hg, bazaar and darcs) so easy, possible. Arch
claimed to have easy branching, but it was still the old explicit model.

(Besides yes, I can confirm that Arch was not the easiest thing to use.)

> The darcs commandset (init, push, pull) is what git, hg and bzr have
> today in common. At least _I_ learned about how it could be easy by
> watching people use Darcs (and feeling very ashamed of my baroque Arch
> usage). The focus on patch tracking (as opposed to "snapshot"
> tracking) and the whole patch algebra are two misfires I'd say.
> Snapshot-tracking DSCMs are winning (faster and fundamentally more
> reliable), and the patch algebra doesn't quite scale and (as far as
> I've heard) sometimes ends in unsolvable corner cases.

IMHO the patch algebra also falls short of it's goal. The idea is supposed to
be that you can cherry-pick easily. However, in practice many changes that
are easy to cherry-pick are textually dependent in something like import
list, list of files in makefile or such. While git cherry-pick will happily
apply such patch and give you a single easy to resolve conflict, darcs will
just insist on pulling the other patch as well.

-- 
						 Jan 'Bulb' Hudec <bulb@ucw.cz>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-06-24 21:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-24  5:32 Darcs Bu Bacoo
2007-06-24 17:59 ` Darcs Linus Torvalds
2007-06-24 20:45   ` Darcs Martin Langhoff
2007-06-24 21:19     ` Jan Hudec [this message]
2007-06-24 21:52     ` Darcs Theodore Tso
2007-06-24 22:22     ` Darcs Junio C Hamano
     [not found]       ` <61e816970706241638j60830741p2cd1a102a72ae226@mail.gmail.com>
2007-06-24 23:40         ` Darcs Dan Chokola
2007-06-25  0:00         ` Darcs Linus Torvalds
2007-06-25  4:44           ` Darcs Dan Chokola
2007-06-27  0:00             ` Darcs Martin Langhoff
2007-06-24 23:21     ` Darcs Linus Torvalds
2007-06-28  1:26   ` Darcs Josh Triplett
2007-06-28 13:02     ` Darcs Johannes Schindelin
2007-06-29  7:13     ` Darcs Bu Bacoo
2007-06-25 11:36 ` Darcs Florian Weimer
2007-06-25 16:54   ` Darcs Bu Bacoo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070624211952.GA3044@efreet.light.src \
    --to=bulb@ucw.cz \
    --cc=bubacoo@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=martin.langhoff@gmail.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).