Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] from svn to git
Date: Tue, 18 Dec 2007 09:40:38 -0800	[thread overview]
Message-ID: <1197997488-sup-6128@south> (raw)
In-Reply-To: <1197970598-sup-7985@ausone.inria.fr>

Excerpts from nicolas.pouillard's message of Tue Dec 18 01:36:47 -0800 2007:
> Nice  move!  However  have you looked at darcs[1]? It's even better
> IMHO, it's smarter, smaller and a lot more easy to understand.
> 
> I maintain a sup darcs repository [2] based on regularly importing the
> svn.

I've actually fantasized about darcs for quite a while (e.g., [1]). I'm
convinced it's better than git in most ways. But the alterior motive
here is for me to get enough experience to introduce something at work,
and darcs's conflict resolution bug pretty much negated that for me. Git
also has going for it its pace of development, operational speed, and
the existence of large, high-profile projects managed by it, which are
really what will convince the crusty neophobe engineers I work with.

The upcoming Darcs 2 [2] may very well fix everything. But in the mean
time, the existence of git-hunk-commit --darcs [3] makes daily git usage
approach tolerability, although I do hold my nose.

[1] http://www.mail-archive.com/darcs-users at darcs.net/msg03431.html
[2] http://article.gmane.org/gmane.comp.lang.haskell.cafe/33159
[3] http://thread.gmane.org/gmane.comp.version-control.git/41033

-- 
William <wmorgan-sup at masanjin.net>


  reply	other threads:[~2007-12-18 17:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-18  7:24 William Morgan
2007-12-18  9:36 ` Nicolas Pouillard
2007-12-18 17:40   ` William Morgan [this message]
2007-12-18 19:42     ` Nicolas Pouillard
2007-12-18  9:49 ` Marcus Williams
2007-12-18 14:40 ` Grant Hollingworth
2007-12-18 20:14   ` William Morgan

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=1197997488-sup-6128@south \
    --to=wmorgan-sup@masanjin.net \
    /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