On Sat, Sep 15, 2012 at 12:26 PM, Kirk, Benjamin (JSC-EG311) <benjamin.kir...@nasa.gov> wrote: >>> Check out Allura - >>> https://sourceforge.net/p/allura/wiki/Features >>> >>> It is a new hosting option for sourceforge projects. For those of you >>> familiar with redmine, it should seem familiar. >>> >>> I'm very interested in migrating to it and using the issue tracking for >>> better integrated development. >>> >>> This is a pretty big move, though, and would like to hear other thoughts... >>> > >> I see they now offer git and hg. Any plan to switch over, or do you >> prefer to stick with svn? > > I bet John could convince me why we should switch to git, but honestly I'd > rather make this move first. Unlike cvs, there is nothing I don't like in > svn versions 1.6 and newer, so I'm not in a hurry to move off it.
I don't have any experience working with a centralized git repo, so I can't comment directly, but I know David Andrs does so maybe he will chime in. I can comment on what I like about using git on top of svn, in the hope it might lead to some of the other active developers to give git a try. What I like most about git is, it really lets you work in "attention deficit disorder" mode. For example, let's say you are working on a relatively involved patch, and have modified several different files, when you get an email from Roy that says, "hey, can you check out this new patch ASAP?". This scenario is kind of tricky to handle in SVN. You can make a patch of your local changes with 'svn diff', stash it somewhere, and then hope to come back to it later. Or you can see if Roy's patch applies cleanly on top of what you are already doing, but this usually isn't a great idea either. Either way you are doing manual source code control, something that the tools are supposed to help you avoid! With git, it's easy. You just "commit" all your current changes. Git commits are all local, so this doesn't affect anyone else's work, and doesn't require network access, etc. Then you can either create a new branch from SVN HEAD, say, and apply Roy's patch (creating a new branch is very easy in git, you do it constantly) or try applying Roy's patch directly on top of your most recent local commit on the same branch. If it doesn't apply cleanly, git will tell you, if it does you can check it out, see if everything's working, let Roy know, and then reset his patch, and you are then back to your original work before the interruption. -- John ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
