From: Linus Torvalds <torvalds@linux-foundation.org>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Bu Bacoo <bubacoo@gmail.com>, git@vger.kernel.org
Subject: Re: Darcs
Date: Sun, 24 Jun 2007 16:21:05 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0706241618490.3593@woody.linux-foundation.org> (raw)
In-Reply-To: <46a038f90706241345m4b5ecb80p9f4ec840993023e0@mail.gmail.com>
On Mon, 25 Jun 2007, Martin Langhoff wrote:
>
> The darcs commandset (init, push, pull) is what git, hg and bzr have
> today in common.
I really think the credit goes to BK, not darcs.
BK is why a lot of git commands look like they do: I didn't want to
re-implement BK, but I definitely wanted to reimplement the flow. At least
for common stuff.
The fact that darcs may have been more usable than other open source scm's
says more about the other open source scm's than it says about darcs.
arch/tla in particular was (is?) horribly messy. I tried to look at it
before starting git, but even just a cursory look convinced me to look
away..
Linus
next prev parent reply other threads:[~2007-06-24 23:21 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 ` Darcs Martin Langhoff
2007-06-24 23:21 ` Linus Torvalds [this message]
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=alpine.LFD.0.98.0706241618490.3593@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=bubacoo@gmail.com \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
/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).