Kurinchi Blogger Scribbles …


Posts Tagged ‘svn’

Feb 01
2010

Choosing version control system (VCS): Git vs Subversion

Last updated: February 1st, 2010

Git

– Distributed repository system (adaptive work flow models)
– Source control taxonomy: DAG storage
– URI to git directory is where the repository is stored and it always has branches and tags
– Repository root folder contains a .git directory which maintains file history
– Scalability
– Faster, Efficient branching and merging
– License: Copyleft

Subversion (SVN)

– Centralized repository system
– Source control taxonomy: Delta storage
– URI to a subversion depository most commonly adopts /trunks, /branches and /tags directories
– Each folder maintains a .svn directory to store the file history
– Not efficient in scaling
– Not efficient in branching and merging
– License: Copyfree

Aug 18
2009

Free resources – Open source code management related

Last updated: August 15th, 2009

Code Revision, Code Management

Subversion (Tigris) Download
http://subversion.tigris.org/getting.html

Open Source Version Control Book
http://svnbook.red-bean.com/

Git Distributed Open Source Version Control Download
http://git-scm.com/download

Git Man Page
http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html

CVS Download
http://www.nongnu.org/cvs/

CVS Help
http://ximbiot.com/cvs/manual/

Apr 09
2009

Subversion SVN: Project organization

Last updated: April 10th, 2009

Subversion Project Organization: Intro

When organizing the repository structure for maintaining the code base, system admins adopt two basic formats for Project organization in subversion. This depends on the needs of the project and it can be varied over a period of time, depending on the scope defined for the code base. Subversion is very flexible in handling these changes and is easier to maintain than most other products in the market. (more…)


Valid HTML 4.01 Strict  Valid HTML 4.01 Strict