From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Dan Chokola" <dan@chokola.com>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Junio C Hamano" <gitster@pobox.com>,
"Bu Bacoo" <bubacoo@gmail.com>,
git@vger.kernel.org
Subject: Re: Darcs
Date: Wed, 27 Jun 2007 12:00:48 +1200 [thread overview]
Message-ID: <46a038f90706261700g7b1791d7r5413d0b289421122@mail.gmail.com> (raw)
In-Reply-To: <61e816970706242144y5dd07464ue6b06478a5920699@mail.gmail.com>
On 6/25/07, Dan Chokola <dan@chokola.com> wrote:
> So, relating back to the original post, and extending on Linus'
> 'academic' analogy, Darcs is like a thesis project from university
> that proves how DSCM can be done scientifically. Git is grown-up Darcs
> that proves how DSCM can be done practically.
I don't think it's like that. More like
- BK showed it's done
- Darcs picked some good bits from BK (while no other foss dscm did
until git/hg/bzr came along) but got distracted with interesting but
not-that-useful stuff - see patch algebra.
cheers,
m
next prev parent reply other threads:[~2007-06-27 0:00 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 ` Darcs Jan Hudec
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 ` Martin Langhoff [this message]
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=46a038f90706261700g7b1791d7r5413d0b289421122@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=bubacoo@gmail.com \
--cc=dan@chokola.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).