[Grecipe-manager-devel] Switching to git
GNOME Recipe Manager w/ nutrition information and other useful plugins
Status: Beta
Brought to you by:
thomas_hinkle
From: Thomas M. H. <tmh...@gm...> - 2009-03-15 01:19:33
|
Dear gourmet enthusiasts, I am just about ready to make the switch to git permanent. I have already activated a git repository for Gourmet and I've imported our CVS history into git. You can access git here: https://sourceforge.net/scm/?type=git&group_id=108118 For my purposes, the main advantage of git is speed -- it is now *much* faster to look at my devel tree, see what's changed, update my changelog appropriately, and commit my changes. The reason for this, as I understand it, is that the whole history is now stored locally for each user, so we depend less on the SF server for our speed ,etc. Git is also known for "distributed development" -- it should make things like branching and merging easier to do for interested parties. This e-mail is both a heads up and a call for any objections. My plan is to go ahead and deactivate our CVS service on SF now in favor of git for the future. Though it's possible to keep both running on SF, it will only lead to confusion in the long term to have more than one version control system. Please let me know if you have any objections to my closing down Gourmet CVS. Note that there are many easy-to-use tools for git, just as there are for SF. For any other emacs users out there, the key for me was finding git.el ( http://www.emacswiki.org/emacs/Git#toc4). With this installed, I can call M-x git-status, which is the equivalent of the old M-x cvs-examine. Otherwise, all my key-commands are the same for doing diffs, commits, etc. Tom |