unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: guile-devel@gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: Switching to Git?
Date: Sat, 25 Aug 2007 15:04:48 -0300	[thread overview]
Message-ID: <46D06F40.6050605@xs4all.nl> (raw)
In-Reply-To: <87lkc47fa1.fsf@pobox.com>

Andy Wingo escreveu:
>> How about switching from CVS to Git [0]?
> 
> The advantages you list are compelling. It is especially good that
> savannah supports git. I have only two points to counter: (1) git sucks
> to use (but somehow many people seem to manage), and (2) git does not
> work on windows.

This is not true. There is a mingw port, which is starting to become usable.
However, I'm a bit mystified why windows support should be a priority for 
GUILE.

As for the user interface, it does have it's edges, but after a couple of
weeks it feels quite natural for common stuff (committing, pulling, pushing,
merging).  I do have to look at the manual for the more exotic commands 
(rebase, pickaxe, etc.)

> As an aside, in GStreamer we are going to completely punt on this
> question, and switch to subversion. You get changesets, which allows
> git-svn, bzr-svn, etc, which are not bad options. That could be the
> correct switch for guile -- there is no downside to switching to
> subversion relative to CVS.

Frankly, I think it's nuts not to go with a distributed system if 
transitioning away from CVS.  The only pertinent question is git or
mercurial. 


-- 
 Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen



_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  parent reply	other threads:[~2007-08-25 18:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-20 21:45 Switching to Git? Ludovic Courtès
2007-08-20 23:49 ` Kevin Ryde
     [not found]   ` <87d4xgyq28.fsf@laas.fr>
2007-08-22  8:14     ` Ludovic Courtès
2007-08-22 13:53     ` Dan McMahill
2007-08-25 18:08   ` Han-Wen Nienhuys
2007-08-21 14:09 ` Greg Troxel
2007-08-25 17:59   ` Han-Wen Nienhuys
2007-08-21 19:17 ` Dan McMahill
2007-08-25 18:14   ` Han-Wen Nienhuys
2007-08-21 21:23 ` Andy Wingo
2007-08-22  2:17   ` Cesar Strauss
2007-08-25 18:04   ` Han-Wen Nienhuys [this message]
2007-08-25 18:11 ` Han-Wen Nienhuys
2007-09-03  0:31 ` Rob Browning
  -- strict thread matches above, loose matches on Subject: below --
2007-08-21 21:56 dsmich
2007-08-25 18:28 ` Han-Wen Nienhuys

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

  List information: https://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=46D06F40.6050605@xs4all.nl \
    --to=hanwen@xs4all.nl \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).