But this was in the context of moving from cvs to svn. If we do move, it is sensible to discuss the options.
2009/6/5 Michael Petch <mpe...@capp-sysware.com>: > I have a simple philosophy. Don't fix what's not broken. Obviously you are not a programmer :) > > On 04/06/09 9:19 PM, "保坂範行" <bgn...@gmail.com> wrote: > >> Hi. >> >> Video: Linus on git >> http://www.youtube.com/watch?v=4XpnKHJAok8 >> Linus damned CVS/SVN in this video. >> I hope that you are not going to kill Linus. :D >> >> hg is an another good choice, too. >> I do not know much about it. >> >>> (e.g. moving around files and keeping a sensible log), >> git mv and git log are not good enough for you? >> git bisect is a great tool. check it out. >> git cvsimport let you import CVS controlled code very easily. >> >> Yes, there is a migration cost, you have to learn if you don't know them. >> >> Nori >> >> >> 2009/6/5 Christian Anthon <christian.ant...@gmail.com>: >>> Hi all, >>> >>> the cvs repository has been restored on savannah. It is from a May 27 backup >>> which matches what I have locally. Feel free to test it, and commit to it. >>> >>> As for moving to a different kind of VCS: I've looked a bit on git, and I >>> don't think it is for us right now. Possibly git has some advantages over >>> svn that I'm not aware of, but I believe subversion can do what we want >>> (e.g. moving around files and keeping a sensible log), and more importantly >>> the subversion clients are much better and more complete than the git ones. >>> >>> As for moving to an alternative to savannah: while the service that savannah >>> provides isn't 100% in quality, I still feel that they have been reasonably >>> reliable and sufficient for our needs, and I know of no other service that >>> follows the GNU philosophy to the degree that savannah does. >>> >>> Christian. >>> >>> _______________________________________________ >>> Bug-gnubg mailing list >>> Bug-gnubg@gnu.org >>> http://lists.gnu.org/mailman/listinfo/bug-gnubg >>> >>> >> >> >> _______________________________________________ >> Bug-gnubg mailing list >> Bug-gnubg@gnu.org >> http://lists.gnu.org/mailman/listinfo/bug-gnubg >> > > > > > _______________________________________________ > Bug-gnubg mailing list > Bug-gnubg@gnu.org > http://lists.gnu.org/mailman/listinfo/bug-gnubg > _______________________________________________ Bug-gnubg mailing list Bug-gnubg@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnubg
