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 14:59:40 -0300 [thread overview]
Message-ID: <46D06E0C.6010103@xs4all.nl> (raw)
In-Reply-To: <rmilkc59dxw.fsf@fnord.ir.bbn.com>
Greg Troxel escreveu:
> 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 have switched from CVS to Git for lilypond development, and it has done wonders
for my stable releases. Since it is extremely easy to cherry-pick patches
between branches, I back/front port all bugfixes. The releases are even
synced: 2.11.29 contains fixes and features, and where possible the same
fixes appear in 2.10.29 (stable version)
> 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?
Decentralized development is a policy decision, and centralized is just as
well possible with git. Even more so, because you can actually track the
the author (the person writing the patch) separately from the committer
(person having write access to the repository). This makes tracking the
copyright status (ie. who wrote what) of a project much more transparent.
--
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
next prev parent reply other threads:[~2007-08-25 17:59 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 [this message]
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=46D06E0C.6010103@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).