From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: guile-devel@gnu.org
Cc: "Andy Wingo" <wingo@pobox.com>, "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: Switching to Git?
Date: Sat, 25 Aug 2007 15:28:28 -0300 [thread overview]
Message-ID: <46D074CC.2080503@xs4all.nl> (raw)
In-Reply-To: <11969026.1187733389365.JavaMail.root@web21>
dsmich@adelphia.net escreveu:
> If there must be a switch, I'd also say that subversion is probably the best way to go.
> Less culture shock for long time cvs users. Windows people aren't left out. Guile doesn't
> really need the massively distributed model that the Linux kernel requires.
Actually, try this for a data point:
git clone git://git.sv.gnu.org/lilypond.git
cd lilypond; gitk
what you will see is the history of LilyPond, which is not massively distributed
by any standard. If you press page down a couple of time, you will see 'parallel'
development and merging of several topics, eg.
- Spacing features by Joe Neeman
- Release fixes by me
- translation updates by John Mandereau and helpers
- doc updates by Graham Percival and helpers
these all happen in parallel. In particular, I am the release coordinator,
and I always make releases which are effectively branches. This means that
I can make small fixes (eg. a make dist failure) to build a release locally
and merge them back into the repository HEAD later. My releases are
not inconvenienced by large hacks that are pushed to the HEAD.
--
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 18:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 21:56 Switching to Git? dsmich
2007-08-25 18:28 ` Han-Wen Nienhuys [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-20 21:45 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
2007-08-25 18:11 ` Han-Wen Nienhuys
2007-09-03 0:31 ` Rob Browning
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=46D074CC.2080503@xs4all.nl \
--to=hanwen@xs4all.nl \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=wingo@pobox.com \
/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).