Another important factor about GIT, is that it's an offline version control. Every person has their own repository, so you if the "online" repository goes down, you have the ability to still properly work on things.
If you are working on a code that others works as well, no one hurt each other as long as it offline, and only when it merges to the "online" repository, it's when you merge all of the code. Another better feature is the way tagging and brunching works. You can mix everything without making a copy of the whole tree all over on each tagging/brunching. and unlike svn, you actually do have differences between the two. And there are even more features, but the question is if it good for all projects. I don't know the answer, I only know that I moved to git in my last new projects, and it helped me a lot when I was in a need to figure out when I destroy something with my committing, on places where svn would not have any history of that. Ido On Tue, Apr 7, 2009 at 4:47 PM, Graeme Geldenhuys <graemeg.li...@gmail.com>wrote: > ---------- Forwarded message ---------- > From: Graeme Geldenhuys <graemeg.li...@gmail.com> > Date: Tue, Apr 7, 2009 at 3:45 PM > Subject: Re: [fpc-pascal] fpGUI Toolkit source repository migrated to Git > To: FPC-Pascal users discussions <fpc-pas...@lists.freepascal.org> > > > On Tue, Apr 7, 2009 at 3:25 PM, Paul Ishenin <webpi...@mail.ru> wrote: > > > > I am wondering what are that needs for project with *the only one > developer* > > that svn cannot serve well and that alone developer need to install > another > > source control system? Imo just a waste of time. And not only your time > but > > SVN does not fit my workflow! It's plain and simple... Git makes my > live easier. > > Lets give a few examples where SVN fails and Git proves much better: > > * I often want to commit only partial changes in a file. Why, because > i was debugging something and added lots of writeln() commands. i > don't want to revert those writeln() immediately because the next bug > hunt would also require them. Under svn I have to create a patch of > all changes for that file. make a copy of the patch and and pick the > hunk I am interrested in. Revert my changes and apply the new modified > patch. Check that all is ok and then commit. Ah, no I need to > re-commit the original patch, so I can get my writeln()'s back. A sh*t > load of work for something that should be simple. Using 'git gui' I > simply right-click the hunk I want to commit and select stage. now > execute 'git commit' and I'm done. How easy was that!! > > * I often work on something that takes a while or experimenting with > someting. Using SVN I can't commit my changes as I work without > affecting the server history. With git I can. And don't mention svn > branches, because they suck! Yes I have tried 'svnmerge.py' which is > simply a band-aid on a big problem. > > * I like to take work home on a pen (flash) drive. I can now simply > clone my work PC repository to the flash drive and work at home. Next > day I simply push changes from pen drive to work PC again. > > * Merging is a lot more intelligent - I seem to get much less conflicts. > > * I love the syntax highlighting in 'diff', 'log', 'show' and 'status' > commands. All built into git. > > * I can't do the following in SVN. In Git I can, and the result is instant! > $ git log --since="1 week ago" --until="yesterday" > > * I can't do the following in SVN: (regular expressions on the actual > diffs) > $ git log --pickaxe-regex -S"some.*code.*change" > > * My internet connection at home is not very fast. Git is a LOT faster > at pushing or pulling changes. Even on our work internet connection > (4Mb line) I can see the speed difference. > > > all other developers who need to update from your repository. Now they > need > > to learn git and to install it on their systems. > > I push to the SourceForge repository and they collect updates from > there... Currently my local repository is off-limits to the public. > > > Regards, > - Graeme - > > > _______________________________________________ > fpGUI - a cross-platform Free Pascal GUI toolkit > http://opensoft.homeip.net/fpgui/ > > > > -- > Regards, > - Graeme - > > > _______________________________________________ > fpGUI - a cross-platform Free Pascal GUI toolkit > http://opensoft.homeip.net/fpgui/ > _______________________________________________ > fpc-other maillist - fpc-other@lists.freepascal.org > http://lists.freepascal.org/mailman/listinfo/fpc-other >
_______________________________________________ fpc-other maillist - fpc-other@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-other
