From: Greg Troxel <gdt@ir.bbn.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Switching to Git?
Date: Tue, 21 Aug 2007 10:09:47 -0400 [thread overview]
Message-ID: <rmilkc59dxw.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <87odh1ribo.fsf@chbouib.org> ("Ludovic Courtès"'s message of "Mon, 20 Aug 2007 23:45:31 +0200")
[I've been using CVS since 1994 and have seen more VC systems come and
go than I can remember. So I'm predisposed to be cranky about
switching.]
My quick reaction is that this would be be good overall. While the
benefits are probably significant, switching makes it harder for people
to follow along. I say this because of my experience with guile-gnome -
they have changed revision control systems several times and I have had
trouble with each one. I no longer track guile-gnome HEAD - just update
pkgsrc to releases and then complain when the latest release doesn't
work with the latest release of some dependency.
The more serious problem with guile is a lack of focus on timely, stable
releases usable by people who want to integrate it. Plus backwards
compatibility so that people that do integrated it have very little
grief, and the current slib mess.
I wonder if the 'decentralized development' notion is really consistent
with the "papers, please" demand of FSF. Have "assigned" projects used
distributed CM systems? How has that been handled?
But if the people that have assigned changes and actually hack on guile
(which isn't me) want to use git, and if it will help the cause of
better releases that can be used in confidence, then that seems fine.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-08-21 14:09 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 [this message]
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
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=rmilkc59dxw.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--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).