From: "Bu Bacoo" <bubacoo@gmail.com>
To: "Florian Weimer" <fw@deneb.enyo.de>
Cc: git@vger.kernel.org
Subject: Re: Darcs
Date: Mon, 25 Jun 2007 18:54:00 +0200 [thread overview]
Message-ID: <cecbdd220706250954m6ce18fcem6cae4729e795e947@mail.gmail.com> (raw)
In-Reply-To: <87vedcqna7.fsf@mid.deneb.enyo.de>
Florian, what are you moving to? To GIT?
On 6/25/07, Florian Weimer <fw@deneb.enyo.de> wrote:
> * Bu Bacoo:
>
> > What do you think about darcs?
>
> The UI is nice, but darcs is quite slow (even if you don't hit the
> exponentional corner case in the merge algorithm).
>
> My main gripe with darcs, and the prime reason why I'm moving away
> from it, is its lack of support for software archaeology. If you
> haven't tagged a tree at some point, you'll face lots of trouble when
> you try to restore something that resembles the tree you had back
> then. This is a direct consequence of the "heap of patches" approach,
> but it's a real nuisance, and the benefits of the increased
> flexibility don't make up for it, IMHO.
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2007-06-25 16:54 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 ` 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 ` Bu Bacoo [this message]
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=cecbdd220706250954m6ce18fcem6cae4729e795e947@mail.gmail.com \
--to=bubacoo@gmail.com \
--cc=fw@deneb.enyo.de \
--cc=git@vger.kernel.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).