Comments on: Git vs SVN for bosses

By: Anonymous

Anonymous — Wed, 11 Nov 2009 08:11:11 +0000

[...] [...]

By: Belug

Belug — Sun, 08 Nov 2009 14:07:23 +0000

Hi, i don’t think there is a debate about witch one is the best between SVN and GIT. The thing is witch one suite the best the need you have. If found this website talking about the pro and con of GIT vs SVN.

http://git.or.cz/gitwiki/GitSvnComparsion

It’s based on SVN 1.5 hope this will help some of you to choose your best!

By: Git-ing Started: My Journey to with Git – j.c. crosby

Git-ing Started: My Journey to with Git – j.c. crosby — Mon, 02 Nov 2009 20:28:53 +0000

[...] Git vs. SVN for Bosses: http://techblog.floorplanner.com/2008/12/09/git-vs-svn-for-bosses/ [...]

By: Sukesh Nambiar

Sukesh Nambiar — Fri, 18 Sep 2009 15:48:35 +0000

I think git vs subversion is a topic that one can debate till the world ends.

I have used both git and subversion. Both has its strength and weakness. I could not find one better than the other.

Git uses distributed repository concept and support private branches and quick merges etc. This is extremely useful handy in indepependent and experimental software development.

Subversion uses centralized repository and is useful for organizations that want to keep the source control very tight and look for an integrated development environment.

All these boils down to your development philosophy. With subversion 1.5, branching is not that very difficult.

So a choice may be made based on your development philosophy and your need. Trying to find the best and using it will not be a viable solution.

By: Being John…uhm…Bader » Blog Archive » Link collection about version control systems

Mon, 03 Aug 2009 10:48:14 +0000

[...] Git vs SVN for bosses (Stupid I think) [...]

By: Matt-W

Matt-W — Thu, 23 Jul 2009 08:00:13 +0000

SVN 1.5 does have merge tracking yes, but it doesn’t have the property of preserving the original authorship attribution on the merged commits, which I consider very important and a primary reason why my workplace should switch to git.

Unfortunately, convincing everyone else we should switch to git, including the management, is not likely to be easy.

By: Gert-Jan

Gert-Jan — Tue, 30 Jun 2009 19:50:02 +0000

I found this presentation of Scott Chacon on git very useful! http://scotland-on-rails.s3.amazonaws.com/1A02_Scott_Chacon.mp4

By: C

Tue, 30 Jun 2009 01:11:52 +0000

So SVN or Git?

Then you have Perforce, Mercurial, Launchpad with Bazaar, Visual Source Safe and so on. (CVS is kind of dead…)

SVN can’t (easily) lock a tree, Git is “all or nothing” access rights (and hates your Windows), others have their own quirks as well.

So again: It depends on the project which one you will use most efficiently.

It would be useful to have a real and objective comparison of these solution, so each project with a short reading could decide which solution is the best for them.

By: Chris

Chris — Fri, 29 May 2009 07:56:41 +0000

If you’re developing in Windows, you may also want to consider Mercurial which gives pretty much the same advantages as Git only with Windows support (TortoiseHg, etc).

By: Kiall

Kiall — Tue, 24 Mar 2009 02:33:02 +0000

humm I always forget certian things will get scrapped by comment filters

to create the branch…
“svn copy URL_TO_TRUNK URL_TO_BRANCH”

to merge the branch back into trunk…
“svn merge –reintegrate URL_TO_TRUNK”