Welcome
The Nomad blog is where we share news of our projects, thoughts on web development and a weekly round up of things on the Internet that have caught our eye - Tales from the Internet
Tag Cloud
2011 accessibility adobe shadow agencies amazon apple arduino backups bears blog boo book review browsers business cablegate captcha charity clients code igniter code snippets community conference contracting cooperation csharp css css3 development dojo dyson eeuk expression engine free full frontal gaming git honey pots html5 installation internet internet explorer ipad iphone java javascript jquery linux little printer ludum dare micro frameworks mobile mono monotouch multi-touch mvc news nomad opengl organic osx passwords performance php process pseudo selectors rdf recovery remote repository responsive design review s3 security seo silverstripe spam spime sublime text 2 svn technology tfi tools trust truth underscore url shortening usability version control wii wikileaks windows
Blog » Version control with GIT - Introduction
Version control with GIT - Introduction
Over the past year or two Git has become an increasingly popular method of version control for the web development community. Subversion has been a popular choice in the industry for a while but it seems a change is happening (or happened, depending if you've already moved to Git). Although Subversion (or SVN as it's commonly referred to) is still a perfectly adequate, it seems the cool kids are using Git.
Git usage isn't all about developers using the latest tech, there's actually good reasoning on why it's becomming so popular:
- Work with your repositories off-line
- Distributed version control
- Fast - incredibly fast at switching, branching and merging
- Compatible with current protocols such as http, ftp, rsync and ssh
- Scalable - Git does not get slower as the project gets larger
Git was originally developed by Linus Torvalds for Linux kernel development after their main version control system of BitKeeper was withdrawn for free usage by Larry McVoy after its protocols had allegedly been reverse engineered.
Linus began work on developing Git on April 3rd 2005, announced the project on April 6th, became self-hosting on April 7th, and the first merge of multiple branches was performed on April 18th!
If you're coming from SVN to Git, it takes a bit of a shift in attitude to how version control works. One of my current contracts is working with a large, multi-national company who's web team is in the middle of this shift - and the developers there are picking up and running with Git quickly.
Over my next few posts I'll be going through installing Git, creating a repository, staging & commiting your changes, as well as working with remote repositories.
Lee Powell
I have over five years development experience, predominantly with client side technology but also more recently with server side languages such as PHP and Python. I've run teams and performed client facing roles as well as being a programmer. I am passionate about accessibility, standards and all things web.
Comments
No one has commented on this page yet.
RSS feed for comments on this page | RSS feed for all comments
