From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Switching to Git?
Date: Mon, 20 Aug 2007 23:45:31 +0200 [thread overview]
Message-ID: <87odh1ribo.fsf@chbouib.org> (raw)
Hi,
How about switching from CVS to Git [0]?
What this would bring us:
* Decentralized Development
As you may know, this would allow every interested user to hack on
their side, pulling changes from the main repository as they see
fit, and promoting their changes whenever they want. This is really
appreciable.
* Off-Line Operation
As a corollary, this would allow off-line operation on the local
copy of the repository.
* Speed and Bandwidth Improvement
Git operates on a local repository, which makes operations very
fast. This is a significant change when one has got used to waiting
for "cvs diff" to complete for ages. ;-)
* Transactional, Changeset-Oriented
Commit operations are transactional and changeset-oriented. Changes
to a collection of files that are committed at the same time do
appear as a single "change set", rather than as separate changes as
with CVS. This means that GNU-style change logs can be generated
automatically using tools like `git2cl' [4].
* Nice Web Interface
See [1] for example.
These are the most obvious benefits.
Note that Git is now supported on Savannah [2]. It's used by various
GNU projects, and also non-GNU projects (one of which is quite famous
;-)).
Han-Wen did a full import of the CVS history into Git some time ago [1].
Note that it preserves tags and branches. This Git repository is kept
in sync with CVS using a cron job that runs on Han-Wen's machine.
However, it is not automatically synchronized in the other direction,
making it inconvenient.
Of course, nothing's black and white and Git has some weaknesses, too.
Most notably, its UI is a bit rough and at least not to everyone's taste
(which can be worked around by using companion tools such as Cogito
[3]).
Opinions?
Thanks,
Ludovic.
[0] http://git.or.cz/
[1] http://repo.or.cz/w/guile.git
[2] http://git.sv.gnu.org/
[3] http://git.or.cz/cogito/
[4] http://repo.or.cz/w/git2cl.git/
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2007-08-20 21:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 21:45 Ludovic Courtès [this message]
2007-08-20 23:49 ` Switching to Git? 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
-- 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=87odh1ribo.fsf@chbouib.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).