This link has been bookmarked by 433 people . It was first bookmarked on 28 Sep 2007, by someone privately.
-
17 May 12
-
14 May 12
-
03 May 12
-
03 Apr 12
-
19 Mar 12
An BeBasic introduction to SVN..
"Version Control (aka Revision Control aka Source Control) lets you track your files over time. Why do you care? So when you mess up you can easily get back to a previous working version." -
24 Jan 12
-
23 Jan 12
-
02 Jan 12
Melissa KendallIntroduction to Source Control for new coops :D
-
13 Dec 11
-
02 Dec 11
-
28 Nov 11
mptsk .A simple visual guide to VCS - with svn examples
svn subversion tutorial versioncontrol guide programming reference howto beginner
-
24 Nov 11
Karsten FroehlichVersion Control (aka Revision Control aka Source Control) lets you track your files over time. Why do you care? So when you mess up you can easily get back to a previous working version.
-
-
23 Nov 11
-
losophy. Eric
-
-
11 Nov 11
-
30 Oct 11
-
13 Oct 11
-
03 Oct 11
-
30 Sep 11
-
27 Sep 11
-
06 Sep 11
vaichidrewar
BetterExplained LEARN RIGHT, NOT ROTE.
Home All Posts About FAQ Contact ebook
All Posts > Guides,Programming
A Visual Guide to Version Control
Version Control (aka Revision Control aka Source Control) lets you track your files over time. Why do you care? So when you mess up you can easily get back to a previous working version.
You’ve probably cooked up your own version control system without realizing it had such a geeky name. Got any files like this? (Not these exact ones I hope).
KalidAzadResumeOct2006.doc
KalidAzadResumeMar2007.doc
instacalc-logo3.png
instacalc-logo4.png
logo-old.png
It’s why we use “Save As”. You want the new file without obliterating the old one. It’s a common problem, and solutions are usually like this:
Make a single backup copy (Document.old.txt).
If we’re clever, we add a version number or date: Document_V1.txt, DocumentMarch2007.txt
We may even use a shared folder so other people can see and edit files without sending them over email. Hopefully they relabel the file after they save it.
So Why Do We Need A Version Control System (VCS)?
Our shared folder/naming system is fine for class projects or one-time papers. But software projects? Not a chance.
Do you think the Windows source code sits in a shared folder like “Windows2007-Latest-UPDATED!!”, for anyone to edit? That every programmer just works in a different subfolder? No way.
Large, fast-changing projects with many authors need a Version Control System (geekspeak for “file database”) to track changes and avoid general chaos. A good VCS does the following:
Backup and Restore. Files are saved as they are edited, and you can jump to any moment in time. Need that file as it was on Feb 23, 2007? No problem.
Synchronization. Lets people share files and stay up-to-date with the latest version.
Short-term undo. Monkeying with a file and messed it up? (That’s just like you, isn’t it?). Throw away your changes and go back to the “last known good” version in the database.
Long-term undo. Sometimes we mess up bad. Suppose you made a change a year ago, and it had a bug. Jump back to the old version, and see what change was made that day.
Track Changes. As files are updated, you can leave messages explaining why the change happened (stored in the VCS, not the file). This makes it easy to see how a file is evolving over time, and why.
Track Ownership. A VCS tags every change with the name of the person who made it. Helpful for blamestorming giving credit.
Sandboxing, or insurance against yourself. Making a big change? You can make temporary changes in an isolated area, test and work out the kinks before “checking in” your changes.
Branching and merging. A larger sandbox. You can branch a copy of your code into a separate area and modify it in isolation (tracking changes separately). Later, you can merge your work back into the common area.
Shared folders are quick and simple, but can’t beat these features.
Learn the Lingo
Most version control systems involve the following concepts, though the labels may be different.
Basic Setup
Repository (repo): The database storing the files.
Server: The computer storing the repo.
Client: The computer connecting to the repo.
Working Set/Working Copy: Your local directory of files, where you make changes.
Trunk/Main: The primary location for code in the repo. Think of code as a family tree — the trunk is the main line.
Basic Actions
Add: Put a file into the repo for the first time, i.e. begin tracking it with Version Control.
Revision: What version a file is on (v1, v2, v3, etc.).
Head: The latest revision in the repo.
Check out: Download a file from the repo.
Check in: Upload a file to the repository (if it has changed). The file gets a new revision number, and people can “check out” the latest one.
Checkin Message: A short message describing what was changed.
Changelog/History: A list of changes made to a file since it was created.
Update/Sync: Synchronize your files with the latest from the repository. This lets you grab the latest revisions of all files.
Revert: Throw away your local changes and reload the latest version from the repository.
Advanced Actions
Branch: Create a separate copy of a file/folder for private use (bug fixing, testing, etc). Branch is both a verb (“branch the code”) and a noun (“Which branch is it in?”).
Diff/Change/Delta: Finding the differences between two files. Useful for seeing what changed between revisions.
Merge (or patch): Apply the changes from one file to another, to bring it up-to-date. For example, you can merge features from one branch into another. (At Microsoft this was called Reverse Integrate and Forward Integrate)
Conflict: When pending changes to a file contradict each other (both changes cannot be applied).
Resolve: Fixing the changes that contradict each other and checking in the correct version.
Locking: Taking control of a file so nobody else can edit it until you unlock it. Some version control systems use this to avoid conflicts.
Breaking the lock: Forcibly unlocking a file so you can edit it. It may be needed if someone locks a file and goes on vacation (or “calls in sick” the day Halo 3 comes out).
Check out for edit: Checking out an “editable” version of a file. Some VCSes have editable files by default, others require an explicit command.
And a typical scenario goes like this:
Alice adds a file (list.txt) to the repository. She checks it out, makes a change (puts “milk” on the list), and checks it back in with a checkin message (“Added required item.”). The next morning, Bob updates his local working set and sees the latest revision of list.txt, which contains “milk”. He can browse the changelog or diff to see that Alice put “milk” the day before.
Visual Examples
This guide is purposefully high-level: most tutorials throw a bunch of text commands at you. Let’s cover the high-level concepts without getting stuck in the syntax (the Subversion manual is always there, don’t worry). Sometimes it’s nice to see what’s possible.
Checkins
The simplest scenario is checking in a file (list.txt) and modifying it over time.
Each time we check in a new version, we get a new revision (r1, r2, r3, etc.). In Subversion you’d do:
svn add list.txt
(modify the file)
svn ci list.txt -m "Changed the list"
The -m flag is the message to use for this checkin.
Checkouts and Editing
In reality, you might not keep checking in a file. You may have to check out, edit and check in. The cycle looks like this:
If you don’t like your changes and want to start over, you can revert to the previous version and start again (or stop). When checking out, you get the latest revision by default. If you want, you can specify a particular revision. In Subversion, run:
svn co list.txt (get latest version)
...edit file...
svn revert list.txt (throw away changes)
svn co -r2 list.txt (check out particular version)
Diffs
The trunk has a history of changes as a file evolves. Diffs are the changes you made while editing: imagine you can “peel” them off and apply them to a file:
For example, to go from r1 to r2, we add eggs (+Eggs). Imagine peeling off that red sticker and placing it on r1, to get r2.
And to get from r2 to r3, we add Juice (+Juice). To get from r3 to r4, we remove Juice and add Soup (-Juice, +Soup).
Most version control systems store diffs rather than full copies of the file. This saves disk space: 4 revisions of a file doesn’t mean we have 4 copies; we have 1 copy and 4 small diffs. Pretty nifty, eh? In SVN, we diff two revisions of a file like this:
svn diff -r3:4 list.txt
Diffs help us notice changes (“How did you fix that bug again?”) and even apply them from one branch to another.
Bonus question: what’s the diff from r1 to r4?
+Eggs
+Soup
Notice how “Juice” wasn’t even involved — the direct jump from r1 to r4 doesn’t need that change, since Juice was overridden by Soup.
Branching
Branches let us copy code into a separate folder so we can monkey with it separately:
For example, we can create a branch for new, experimental ideas for our list: crazy things like Rice or Eggo waffles. Depending on the version control system, creating a branch (copy) may change the revision number.
Now that we have a branch, we can change our code and work out the kinks. (“Hrm… waffles? I don’t know what the boss will think. Rice is a safe bet.”). Since we’re in a separate branch, we can make changes and test in isolation, knowing our changes won’t hurt anyone. And our branch history is under version control.
In Subversion, you create a branch simply by copying a directory to another.
svn copy http://path/to/trunk http://path/to/branch
So branching isn’t too tough of a concept: Pretend you copied your code into a different directory. You’ve probably branched your code in school projects, making sure you have a “fail safe” version you can return to if things blow up.
Merging
Branching sounds simple, right? Well, it’s not — figuring out how to merge changes from one branch to another can be tricky.
Let’s say we want to get the “Rice” feature from our experimental branch into the mainline. How would we do this? Diff r6 and r7 and apply that to the main line?
Wrongo. We only want to apply the changes that happened in the branch!. That means we diff r5 and r6, and apply that to the main trunk:
If we diffed r6 and r7, we would lose the “Bread” feature that was in main. This is a subtle point — imagine “peeling off” the changes from the experimental branch (+Rice) and adding that to main. Main may have had other changes, which is ok — we just want to insert the Rice feature.
In Subversion, merging is very close to diffing. Inside the main trunk, run the command:
svn merge -r5:6 http://path/to/branch
This command diffs r5-r6 in the experimental branch and applies it to the current location. Unfortunately, Subversion doesn’t have an easy way to keep track of what merges have been applied, so if you’re not careful you may apply the same changes twice. It’s a planned feature, but the current advice is to keep a changelog message reminding you that you’ve already merged r5-r6 into main.
Conflicts
Many times, the VCS can automatically merge changes to different parts of a file. Conflicts can arise when changes appear that don’t gel: Joe wants to remove eggs and replace it with cheese (-eggs, +cheese), and Sue wants to replace eggs with a hot dog (-eggs, +hot dog).
At this point it’s a race: if Joe checks in first, that’s the change that goes through (and Sue can’t make her change).
When changes overlap and contradict like this, the VCS may report a conflict and not let you check in — it’s up to you to check in a newer version that resolves this dilemma. A few approaches:
Re-apply your changes. Sync to the the latest version (r4) and re-apply your changes to this file: Add hot dog to the list that already has cheese.
Override their changes with yours. Check out the latest version (r4), copy over your version, and check your version in. In effect, this removes cheese and replaces it with hot dog.
Conflicts are infrequent but can be a pain. Usually I update to the latest and re-apply my changes.
Tagging
Who would have thought a version control system would be Web 2.0 compliant? Many systems let you tag (label) any revision for easy reference. This way you can refer to “Release 1.0″ instead of a particular build number:
In Subversion, tags are just branches that you agree not to edit; they are around for posterity, so you can see exactly what your version 1.0 release contained. Hence they end in a stub — there’s nowhere to go.
(in trunk)
svn copy http://path/to/revision http://path/to/tag
Real-life example: Managing Windows Source Code
We guessed that Windows was managed out of a shared folder, but it’s not the case. So how’s it done?
There’s a main line with stable builds of Windows.
Each group (Networking, User Interface, Media Player, etc.) has its own branch to develop new features. These are under development and less stable than main.
You develop new features in your branch and “Reverse Integrate (RI)” to get them into Main. Later, you “Forward Integrate” and to get the latest changes from Main into your branch:
Let’s say we’re at Media Player 10 and IE 6. The Media Player team makes version 11 in their own branch. When it’s ready and tested, there’s a patch from 10 – 11 which is applied to Main (just like the “Rice” example, but a tad more complicated). This a reverse integration, from the branch to the trunk. The IE team can do the same thing.
Later, the Media Player team can pick up the latest code from other teams, like IE. In this case, Media Player forward integrates and gets the latest patches from main into their branch. This is like pulling in the “Bread” feature into the experimental branch, but again, more complicated.
So it’s RI and FI. Aye aye. This arrangement lets changes percolate throughout the branches, while keeping new code out of the main line. Cool, eh?
In reality, there’s many layers of branches and sub-branches, along with quality metrics that determine when you get to RI. But you get the idea: branches help manage complexity. Now you know the basics of how one of the largest software projects is organized.
Key Takeaways
My goal was to share high-level thoughts about version control systems. Here are the basics:
Use version control. Seriously, it’s a good thing, even if you’re not writing an OS. It’s worth it for backups alone.
Take it slow. I’m only now looking into branching and merging for my projects. Just get a handle on using version control and go from there. If you’re a small project, branching/merging may not be an issue. Large projects often have experienced maintainers who keep track of the branches and patches.
Keep Learning. There’s plenty of guides for SVN, CVS, RCS, Git, Perforce or whatever system you’re using. The important thing is to know the concepts and realize every system has its own lingo and philosophy. Eric Sink has a detailed version control guide also.
These are the basics — as time goes on I’ll share specific lessons I’ve learned from my projects. Now that you’ve figured out a regular VCS, try an illustrated guide to distributed version control.
253 Comments
SEPTEMBER 27, 2007
OTHER POSTS IN GUIDES,PROGRAMMING
BREVITY IS BEAUTIFUL
AHA! MOMENTS WHEN LEARNING GIT
A BETTEREXPLAINED GUIDE TO CALCULUS
AHA! MOMENTS WHEN LEARNING GIT
A SIMPLE INTRODUCTION TO COMPUTER NETWORKING
INTRO TO DISTRIBUTED VERSION CONTROL (ILLUSTRATED)
RSS OR EMAIL SUBSCRIPTION | PRINT THIS POST
BetterExplained: Get the eBook
Like the site? Take it with you. Develop your math sense using insights, not memorization.
Get the Premium Version of this Article
Professionally-formatted PDF & ePub/Mobi ebook
Screencast video walking through the key highlights
Original PowerPoint slides for all diagrams
Permission to re-use the article in a professional environment (corporate training, etc.)
Learn More
253 Comments »
Trackbacks & Pingbacks
Pingback by Visual guide to version control « Dyan’s Weblog — September 28, 2007 @ 7:11 am
Pingback by digresjon.net | Guide til subversion — September 28, 2007 @ 1:54 pm
Pingback by The Abarentos Narrative » links for 2007-09-28 — September 28, 2007 @ 4:17 pm
Pingback by joet3ch.com » Version Control — September 28, 2007 @ 4:22 pm
Pingback by links for 2007-09-28 at graemef.com — September 28, 2007 @ 4:36 pm
Pingback by Version Control Explained < Nerdpocalypse — September 28, 2007 @ 5:02 pm
Pingback by links for 2007-09-29 « Simply… A User — September 28, 2007 @ 5:32 pm
Pingback by Art, Algorithms, and Design» Blog Archive » Basic Intro to Version Control - Subversion/SVN — September 28, 2007 @ 7:22 pm
Pingback by Karl’s Place » Blog Archive » Cool site: BetterExplained.com — September 28, 2007 @ 7:24 pm
Pingback by links for 2007-09-29 « Donghai Ma — September 28, 2007 @ 9:17 pm
Pingback by Intro to VCS « A Programmer’s Ramblings … — September 29, 2007 @ 2:39 am
Pingback by Version Control: Get a better understanding of version control … | Tolagomi News — September 29, 2007 @ 5:08 am
Pingback by links for 2007-09-29 « D e j a m e S e r — September 29, 2007 @ 8:20 am
Pingback by Sam’s Updates » Blog Archive » links for 2007-09-29 — September 29, 2007 @ 8:26 am
Pingback by Craig Vidler | Weblog » links for 2007-09-29 — September 29, 2007 @ 11:18 am
Pingback by christian schorn » Blog Archive » Links vom 29.09.2007 — September 29, 2007 @ 2:19 pm
Pingback by links for 2007-09-29 « steinarcarlsen — September 29, 2007 @ 2:22 pm
Pingback by Best of Feeds - 30 links - programming, productivity, code, socialsoftware, socialnetworking « Internet Duct Tape — September 29, 2007 @ 5:46 pm
Pingback by links for 2007-09-30 « Mandarine — September 29, 2007 @ 9:27 pm
Pingback by links, ideas and geek stuff » Blog Archive » links for 2007-10-01 — September 30, 2007 @ 5:33 pm
Pingback by Phil Gainley » Blog Archive » A Visual Guide To Version Control With Phil Gainley — October 1, 2007 @ 12:14 am
Pingback by A Visual Guide to Version Control | BetterExplained « vincenthome’s Software Development — October 5, 2007 @ 7:34 am
Pingback by What do you want Better Explained? | BetterExplained — October 7, 2007 @ 10:52 am
Pingback by Wagner Elias - Think Security First » Controle de Versão — October 10, 2007 @ 12:14 pm
Pingback by A Visual Look at Distributed Version Control | BetterExplained — October 15, 2007 @ 12:01 am
Pingback by links for 2007-10-17 — October 17, 2007 @ 4:18 pm
Pingback by Revision Control 101 « Nano Taboada — October 17, 2007 @ 7:06 pm
Pingback by links for 2007-12-13 at DeStructUred Blog — December 12, 2007 @ 7:19 pm
Pingback by Backups « Bhushan G Ahire’s Weblog — December 13, 2007 @ 2:45 am
Pingback by Principle #1 - Builds should be repeatable (Part 2) — Sauers Technologies — December 13, 2007 @ 5:12 am
Pingback by Understanding Software Development « Panospace’s Weblog — January 20, 2008 @ 7:51 am
Pingback by Mind Gravy » Blog Archive » links for 2008-01-24 — January 24, 2008 @ 5:28 am
Pingback by Wildbit » Blog Archive » Visual Guide to Version Control – Social Networking and Subscriber-based Services. — February 13, 2008 @ 9:30 am
Pingback by Effortless version control for teams and one-man developer shops alike | fonicmonkey — February 16, 2008 @ 3:22 am
Pingback by RAILroading » Blog Archive » links for 2008-02-17 — February 16, 2008 @ 8:48 pm
Pingback by a work on process » links for 2008-02-17 — February 16, 2008 @ 9:23 pm
Pingback by Top of the Mountains » Blog Archive » Human-faced beanstalks — February 19, 2008 @ 4:02 pm
Pingback by being (no)body » m3talink for February 24th through February 25th — February 25, 2008 @ 5:56 pm
Pingback by A great intro guide to version control « kfarr — February 29, 2008 @ 11:01 pm
Pingback by Subversion Obliterate, the forgotten feature — March 1, 2008 @ 1:28 pm
Pingback by links for 2008-03-12 « D e j a m e S e r — March 12, 2008 @ 8:18 am
Pingback by Revue de presse | Simple Entrepreneur — March 28, 2008 @ 11:47 pm
Pingback by Incoherent Babbling » Blog Archive » Version Control Explained Simply — April 11, 2008 @ 4:34 pm
Pingback by A Guide to Using Subversion - /dev/null — May 1, 2008 @ 11:36 am
Pingback by Software By Richard » In the Trenches, What is the Best Source Control for My Team? — May 7, 2008 @ 11:48 pm
Pingback by Get your development under control - all about version control — andrewmccall.com — July 22, 2008 @ 6:46 am
Pingback by ScribbleWiki » Blog Archive » Code Management — August 4, 2008 @ 1:39 pm
Pingback by Understanding Version Control Systems « 404 Tech Support — August 20, 2008 @ 3:48 pm
Pingback by Version Control Explained « Frontier Label Web Development Blog — August 28, 2008 @ 12:32 pm
Pingback by Guía visual para el control de versiones « Hermoso día… — August 29, 2008 @ 2:45 am
Pingback by adaptive path » blog » Adaptive Path » Signposts for the Week Ending August 29, 2008 — August 29, 2008 @ 5:29 pm
Pingback by nortypig » Blog Archive » A Visual Guide to Version Control — September 3, 2008 @ 4:23 am
Pingback by Pragmatic Yankee » Blog Archive » links for 2008-09-04 — September 4, 2008 @ 11:03 am
Pingback by PeopleSoft Wiki: PeopleTools Version Control — September 20, 2008 @ 1:13 am
Pingback by A Practical Guide to University → Valhalla Island — October 7, 2008 @ 1:56 am
Pingback by [ mkhairul.com ] » Adding a new feature to a project — November 6, 2008 @ 1:15 am
Pingback by Toyota Jidoka dan Continuous Integration « Ha–Dhiku–suma Wahab Blog — November 10, 2008 @ 8:29 am
Pingback by things to look at (November 17th - November 20th) | stimulant - changing things around. . . — November 20, 2008 @ 1:02 am
Pingback by A Leased Line to the Collective Unconscious » Subversion for web design - how we do it @ Karyx — December 3, 2008 @ 9:31 am
Pingback by Technical Related Notes » Blog Archive » links for 2007-09-29 — January 11, 2009 @ 5:56 pm
Pingback by Building the ideal web development environment « Zulu 7 — January 13, 2009 @ 5:07 pm
Pingback by 版本控管流程圖解 « Odds@Blog — January 19, 2009 @ 1:56 am
Pingback by 版本控管圖解 « 月光之東 — January 19, 2009 @ 4:07 am
Pingback by links for 2009-02-20 - Paul Griffin Petty — February 20, 2009 @ 6:01 am
Pingback by links for 2009-03-04 | BlueWave Media - BlueWave Media Cafe — March 6, 2009 @ 5:59 am
Pingback by links for 2009-03-07 « techGOVERN — March 7, 2009 @ 5:33 pm
Pingback by Silvestro Fantacci: Linux C++ IDE — March 21, 2009 @ 12:59 pm
Pingback by Intro to Git for Web Designers | Webdesigner Depot — March 26, 2009 @ 12:19 am
Pingback by Intro to Git for Web Designers | Feed Reader (Beta) — March 26, 2009 @ 9:14 am
Pingback by » 向网站设计师们介绍Git — April 10, 2009 @ 9:42 am
Pingback by Monday, May 11, 2009 | shiner.clay — May 12, 2009 @ 2:09 pm
Pingback by Version Control, Google Documents, and Meaningful Commits « Mcstrother's Blog — May 31, 2009 @ 7:20 pm
Pingback by A Visual Guide to Version Control | Kyle Wu 的网络日志 — July 14, 2009 @ 11:50 pm
Pingback by Intro to Distributed Version Control (Illustrated) | Kyle Wu 的网络日志 — July 15, 2009 @ 6:26 pm
Pingback by Mark’s Blog » increasing productivity – part 2: Subversion — August 2, 2009 @ 2:56 am
Pingback by QuickLinks vom 18. August bis zum 19. August — instant-thinking.de — August 19, 2009 @ 4:02 am
Pingback by Baby steps with Subversion | A Stata Mind — August 19, 2009 @ 8:39 am
Pingback by Twitter Trackbacks for A Visual Guide to Version Control | BetterExplained [betterexplained.com] on Topsy.com — August 27, 2009 @ 7:59 pm
Pingback by The Ultimate Guide to Version Control for Designers | MisrIT Reader (Beta) — September 3, 2009 @ 2:59 am
Trackback by paradox1x — November 14, 2009 @ 8:03 pm
Pingback by The ultimate guide to version control for designers « PixelNovel Blog — November 26, 2009 @ 3:32 am
Pingback by How to get up and running quickly with GIT – a Fast, Distributed Version Control System. « the seeker’s quill — March 6, 2010 @ 9:09 pm
Pingback by Aha! Moments When Learning Git | BetterExplained — March 10, 2010 @ 8:02 am
Pingback by Destillat #12 | duetsch.info - Open Source, Wet-, Web-, Software — March 13, 2010 @ 2:14 am
Trackback by uberVU - social comments — March 19, 2010 @ 2:14 pm
Pingback by increasing productivity – part 2: Subversion « qKAI project blog — March 24, 2010 @ 5:23 am
Pingback by Wavesat uses Bazaar « Futurile — April 20, 2010 @ 4:55 am
Pingback by Advanced research paper editing with Subversion revision control : Granthinām — April 20, 2010 @ 10:05 am
Pingback by Blog.us.es | Blog | Control de versiones con Subversión — May 29, 2010 @ 1:21 pm
Pingback by Control de versiones con Subversion — May 29, 2010 @ 1:24 pm
Pingback by BenDauphinee.com Version Control – A Visual Guide « — June 14, 2010 @ 12:23 pm
Pingback by Simple Version Control with TortoiseSVN | IndyVision.Net — September 26, 2010 @ 4:24 pm
Pingback by Tweets that mention A Visual Guide to Version Control | BetterExplained -- Topsy.com — September 28, 2010 @ 3:20 pm
Pingback by Simple Version Control with TortoiseSVN – Part 2 | IndyVision.Net — September 29, 2010 @ 3:19 am
Pingback by 10 types of Git resources, references, tutorials for 10 types of people | Tips Tank — October 3, 2010 @ 6:58 am
Pingback by uforepublic DevBlog » subversion: Linksammlung 4 — October 25, 2010 @ 6:25 am
Pingback by Source Control Rocks! | Thomas Vochten — November 14, 2010 @ 12:48 pm
Pingback by Choosing a Project Management Tool « Automatic Ramblings — November 25, 2010 @ 2:19 am
Pingback by A Visual Guide To Version Control | Pirate Gaspard — December 7, 2010 @ 7:06 am
Pingback by Toyota Jidoka dan Continuous Integration | sedayane — December 19, 2010 @ 6:25 pm
Pingback by Daily del.icio.us for December 19th through December 23rd — Vinny Carpenter's blog — December 23, 2010 @ 6:07 pm
Pingback by How to apply for Google Summer of Code – A byte of note | Sarath Lakshman — March 27, 2011 @ 10:06 pm
Pingback by Becoming a web developer – Version Control Systems (VCS) | Richard Askew — April 25, 2011 @ 12:27 am
Pingback by Setting Up a Flash Development Sandbox: Part 1 | Tut Free — May 22, 2011 @ 2:41 am
Pingback by Subversion explicado visualmente em 30s — June 17, 2011 @ 6:11 am
Pingback by SVN: What's a good, simplified SVN tutorial for someone new to version control? - Quora — June 24, 2011 @ 4:56 pm
Pingback by Starting small | Maarifa — June 30, 2011 @ 7:31 pm
Pingback by A Visual Guide to Version Control | prinjumon — July 8, 2011 @ 1:46 am
Pingback by Opinion: Students, Version Control! | Contains Games — July 11, 2011 @ 3:22 am
Pingback by A Visual Guide to Version Control — Log — August 6, 2011 @ 10:22 am
Pingback by Starting small with collaborative solutions | Collaboration for Good — September 6, 2011 @ 9:47 am
Comments
I absolutely love a Friday but this article has made my day already! Thanks for putting this together…going to have a read of this later on today.
C
Carlton Dickson — September 28, 2007 @ 12:44 am
Great article Khalid, and thanks for the link to Eric’s articles, they were pretty good too!
I will be testing the tagging and branching approach you both mention, it will mean I can check out a branch (i.e. previous release) into a new folder…make bug fixes and check it back into the branch and deploy to live server in a more controlled, and traceable way. Then would obviously need to merge bug fixes into my current trunk (development work since last version).
Here is quite a useful resource for SVN and source control in general by the way http://svnbook.red-bean.com/
Carlton Dickson — September 28, 2007 @ 8:47 am
Hi Carlton, thanks for dropping by! Yep, I’m working out my own branching/merging scheme to make it easy to edit/update the live version while still doing new development. Let me know if you have any insights
Hi Mark, thanks for the comment and link — I hadn’t seen that SCM before.
Kalid — September 28, 2007 @ 9:04 am
Wow.. you are a breath mint!
A Life-saver to be exact.. I’ve been looking for something like this for day..
Thanks!
Skid Vis — September 28, 2007 @ 9:10 am
That was very tasty. Thank you.
Tony — September 28, 2007 @ 9:36 am
Thanks guys! Not sure what’s happening with the food theme (lifesavers, tasty articles) but I’m happy to oblige
(EDIT: Wow, I had been re-reading the article so many times that I forgot food items were the examples I used! They just became a series of words to me.)
Kalid — September 28, 2007 @ 9:59 am
Great Read
Amit — September 28, 2007 @ 11:04 am
Thanks Amit, glad you liked it.
Kalid — September 28, 2007 @ 11:44 am
Great article. Just curious what tool you used for diagramming.
Kevin — September 28, 2007 @ 12:10 pm
thanks for the outline. really helped me grasp the fundamentals.
Mario — September 28, 2007 @ 1:24 pm
I’m using svn that’s more than a year now and I love it. Thanks for that refreshing tuto, it makes its learning for the novice a real pleasure
karim — September 28, 2007 @ 1:39 pm
Nice article.
May I ask where did you do that neat graphics?
Thanks,
Tiago Serafim — September 28, 2007 @ 4:05 pm
Hi all, thanks for the comments. Ack, you want to know the secret sauce? Microsoft Paint.
Just kidding . I make the diagrams in PowerPoint 2007, by drawing various shapes, arranging and styling them appropriately. If you like, check out this article:
http://betterexplained.com/articles/an-intuitive-guide-to-exponential-functions-e/
and the corresponding PowerPoint file:
http://betterexplained.com/examples/graphics/Exponential-growth.pptx
Kalid — September 28, 2007 @ 7:35 pm
yes, I’ve the same question (that caused a-ha moment ) what tool do you use to make such a nice web2.0ish graphics ?
Thanks
Kalyan
Kayan — September 28, 2007 @ 7:43 pm
fabulous read, Thanks tons for putting this together
venki — September 28, 2007 @ 9:07 pm
@Kalyan: I used PowerPoint 2007 — there’s more details in comment #14, above.
@venki: Thanks for the comment, it was a lot of fun to write.
Kalid — September 28, 2007 @ 10:16 pm
Great post! Thanks for doing this.
Sam Jones — September 29, 2007 @ 7:21 am
Thanks Sam, you’re more than welcome.
Kalid — September 29, 2007 @ 9:29 am
Thank you for your wonderful effort.
Ed — September 29, 2007 @ 9:36 am
Hi Ed, thanks for the support.
Kalid — September 29, 2007 @ 9:53 am
Is there a VCS that doesn’t require a server environment? Something that I can use with Visual Studio 2005 for C#
Carlo — September 29, 2007 @ 2:50 pm
Great detail of how the version control works. Thanks for time to put this together.
brian — September 29, 2007 @ 6:35 pm
Great article!
I’d like to add my grain of salt here. If you read this and you thought “oh well, a version control system is probably hard to install” (with the server, etc.).
I strongly suggest you try Mercurial (www.selenic.com/mercurial) or Bazaar (bazaar-vcs.org).
You can initiate a repository in any directory with one command. No fuss. You’re then ready to commit, undo at will, as explained in the article.
On the other hand if you ever need to setup a main server you can too. The point I want to get across is simply that using a “distributed” VCS nullifies the barrier to entry. Want a repo, anywhere? Type ‘bzr init’ or ‘hg init’. Done!
webmat — September 29, 2007 @ 8:03 pm
Oh, and Carlo, I think both my suggestions will satisfy your need. I currently work with Bazaar at work when working on my code, and I use VS2005 with C#.
If you want a graphical user interface you might want to check for TortoiseBzr, which is a graphical front-end for Bazaar. http://bazaar-vcs.org/TortoiseBzr
I haven’t had the time to use it yet, though.
webmat — September 29, 2007 @ 8:09 pm
@Brian: Thanks, glad you liked it!
@webmat: Great tips, thanks for sharing! (This is exactly what I hoped would happen — people sharing their personal tips, tricks and favorites).
@Carlo: Try out webmat’s suggestions. I know Visual Studio has plugins for various VCS systems like SVN, they may have Bazaar or Mercurial as well. This makes it easy to see the status of the project you are working on, inside of Visual Studio.
Kalid — September 29, 2007 @ 10:17 pm
While this looks like a nice introduction to the CVS and SVN model of version control, it’s pretty specific to this model.
The “All version control systems involve the following concepts” part is certainly false unless you exclude distributed version control, systems that don’t directly track files (eg Git), systems that don’t use revisions (eg Darcs), and probably other categories.
Anonymous — September 30, 2007 @ 12:05 am
Hi, thanks for the feedback. Yes, this guide was meant to give an intro to the most common VCS concepts. I wasn’t that familiar with distributed and other systems, but it seems they can have different behavior — I may do a follow up on them. Till then, I’ll caveat the sentence with “Most” vs “All” .
Kalid — September 30, 2007 @ 8:30 am
Thanks this is great for non tech folk
Gareth — October 1, 2007 @ 1:08 am
Hi,
Its awesome, I have already recommended to all newbies around me to refer it.
good stuff. How about writing same thing for a distributed version control.
dextrous — October 1, 2007 @ 3:01 am
thanks for this great tutorial. Makes a lot of sense really quick.
shawn — October 1, 2007 @ 10:54 am
Gareth and shawn, thanks for the comments. I’m thrilled when concepts can shine through, I really believe any subject should be made sensible to everyone
Dextrous, I don’t know much about distributed version control systems, but am excited to learn about them. I’d love to write more once I figure them out.
Kalid — October 1, 2007 @ 2:51 pm
very well explained indeed !!!!
Sagar Mehta — October 2, 2007 @ 12:11 am
Thanks Sagar, glad it was useful for you.
Kalid — October 2, 2007 @ 8:55 am
The content is good, but I was more impressed with the simplicity with which it is presented …
A lot to learn for potential tutorial writers
Sagar Mehta — October 4, 2007 @ 3:28 pm
Thanks Sagar — I find it helps to relate new material to what people already know (like versioning their files by changing the filename). Eventually I’d like to do a tutorial on how to do a tutorial
Kalid — October 4, 2007 @ 6:30 pm
thank you for the article! I’ve used CVS for 2 years, but I’ve got clear understanding of branches and merging only now
Tanya — October 21, 2007 @ 7:12 pm
Great Tanya, I’m glad you found it useful!
Kalid — October 21, 2007 @ 9:24 pm
Kalid, very good intro article. I wrote “Get up and running with TortoiseSVN and Subversion in 15 minutes” a while back which will be of interest to folks starting out with SubVersion. You can find at: http://blog.surfulater.com/2007/02/28/get-up-and-running-with-tortoisesvn-and-subversion-in-15-minutes/
Neville Franks — October 22, 2007 @ 12:04 am
Hi Neville, thanks for dropping by. This article was about the high level concepts, so it’s nice to learn how to set up the nitty-gritty
Kalid — October 22, 2007 @ 1:21 am
Found this article while hunting for a useable distinction between Document Version and Document Revision. Any takers out there?
Paul Ziakin — December 14, 2007 @ 3:05 pm
Hi Paul, unfortunately the words “version” and “revision” seem to be used interchangibly in the sources I’ve found. It might depend on the particular version/revision control tool you are using .
Kalid — December 17, 2007 @ 2:15 pm
Great post! Using straight to the point explanations, attractive visual aids, and command-line examples really helped make the fundamentals easy to understand!
Great work!
Dan — January 25, 2008 @ 7:20 am
Thanks Dan! I try to use as many techniques as I can (diagrams, text, etc.) since people learn differently. Glad it worked for you!
Kalid — January 25, 2008 @ 10:47 am
Thanks man, this is an excellent primer, just what I needed !
Ferdinand — February 17, 2008 @ 8:28 am
Thanks Ferdinand, glad it worked for you.
Kalid — February 17, 2008 @ 11:32 am
please, if possible, add a visual guide (picture/diagram) for concept of conflict.
user — March 25, 2008 @ 12:47 am
Great article!
Being a user of CVS and SVN for years, I always have some difficulties trying to explain it to my collegues and friends, it will help me a lot!
May I translate it into french and publish it on my weblog, with a link to your original?
Nicolas Hoizey — March 31, 2008 @ 1:13 am
Hi Nicolas, thanks for the comment, glad you enjoyed it. Sure, you can translate it, thanks for asking.
Kalid — March 31, 2008 @ 11:19 am
well explained, i like the use of diagrams. The presentation also looks very professional, thanks!
MB — April 28, 2008 @ 6:26 pm
Thanks MB!
Kalid — April 28, 2008 @ 6:55 pm
*T*H*A*N*K*S*
Dave — April 29, 2008 @ 5:54 am
Hi Dave, you’re welcome .
Kalid — April 29, 2008 @ 10:36 am
Yeah, guys! CVS is a very useful tool for any of you who works with a single file during a long time while “building” its definitive content.
However, CVS has the inconvenient of expecting to be you (the user) the one who carries out the check-in and check-out operations.
I have found a very important tool name Live!Doc Personal Edition (www.mylivedocuments.net) which automatically carries out check-in operations and transparently keeps all the changes done in any of your files.
I suggest you to test it …
FHierro — May 17, 2008 @ 9:15 am
amazing read! great job!
Ambar — May 30, 2008 @ 9:46 am
Thanks Ambar, glad you liked it!
Kalid — May 30, 2008 @ 10:04 am
THE BEST GUIDE FOR VCS I’ve seen.. Great great stuff…. thanks a billion
Dilan — June 5, 2008 @ 9:43 pm
Thanks Dilan, you’re welcome!
Kalid — June 5, 2008 @ 10:58 pm
What a nice paper!
ggyy_sun — June 9, 2008 @ 11:21 pm
Thanks, glad you enjoyed it.
Kalid — June 10, 2008 @ 11:11 am
Great article, really good for a version control newbie like myself.
Bedrich — June 10, 2008 @ 1:31 pm
Thanks Bedrich, glad it was helpful.
Kalid — June 11, 2008 @ 2:01 am
Excellent job! One suggestion though …
I’ve always used a visual diff program so I was confused for a while on your explanation of the diff process. I think it would help if you pointed out that diffing r6 with r7 would generate:
+rice
-bread
That is, the diff things you deliberately removed bread. How could it know the difference?
So, when we’re ready to merge we want to know the difference between the file we started with on our branch and the final version on our branch. Then we merge those differences with the latest version on the trunk.
Something like that. A bit more “theory” of what we’re trying to do.
This really helped me solidify the process in my head. Thanks,
Peace,
Rob:-]
Rob — July 2, 2008 @ 10:53 am
“Who would have thought a version control system would be Web 2.0 compliant? Many systems let you tag (label) any revision for easy reference”
Please, this is not remotely like folksonomic tagging in the Web 2.0 sense. If this is a joke, it’s going to confuse the heck out of people who’ve not encountered version control before.
Tim — August 31, 2008 @ 1:33 am
This is a great introduction to VCS! Source code management can be so complicated to explain, but you have made it quite clear.
I would like to see a similar explanation of “distributed” VCS systems. I have read about them, but I have not been able to make any sense of them — they seem like trying to play volleyball when every player has her own ball. I don’t see how it can possibly be anything other than a cluster-you-know-what. But they obviously work for some projects, and I would really like that explained.
Scartaris — September 5, 2008 @ 8:27 pm
Oh! There is a link to an explanation of “distributed” version control right at the end! Thanks!
Scartaris — September 5, 2008 @ 8:33 pm
Thank you very much for this great resource – I will definitely point it to my colleagues so that they learn about source control.
Much thanks!
Ammar — October 31, 2008 @ 8:02 am
@Scartaris: No problem, glad you found it.
@Ammar: Glad you enjoyed it!
Kalid — November 18, 2008 @ 1:23 am
Thank you! This is good stuff. -j
Jeff — December 2, 2008 @ 5:03 pm
It was very helpful
I have a question …
In any of the file header say a *.c file I want to maintain the comments of commiting is it possible to do that automatically…?
by putting a directive as or something similar …?
for example, have a file header as
// file name : xxx.c
// auther : xyz
// creation date : dd mm yy
// revisions : date – comment
// 1.0 : dd-mm-yy – base version
// 1.1 : dd-mm-yy – trying auto-version
// :
thanks in advance
ryth
Rythums — December 8, 2008 @ 12:00 am
@Jeff: You’re welcome.
@Rythums: Offhand, I don’t know of a simple way to prepend the comments to the file (ironically, that would make the file have a new revision, right?). In general, the source control system should probably be used to view the log/history of a file.
Kalid — December 9, 2008 @ 6:35 pm
This is fantastic. I’ve been interested in using version control at the office but I’m pretty sure our IT team thinks it’s not worth it for my needs (more along the lines of grocery lists than software development). Do you know of any program that does this sort of thing at a more basic level, for everyday users?
Love the site, great idea.
Tracy — February 12, 2009 @ 10:54 am
It is such a treat to read a documents like this. Kalid, you rock!!
Manish — February 13, 2009 @ 2:48 am
@Tracy: Thanks for the comment. Subversion is probably the simplest system to use (it has plugins like TortoiseSVN for Windows so you don’t need to use the command line).
@Manish: Thanks!
Kalid — February 13, 2009 @ 5:30 pm
Thanks for this! I understand the topic but haven’t found a better guide yet. So many times I tried to explain the concept and haven’t succeeded in doing so. I’ll try this guide next time.
imissmyjuno — March 4, 2009 @ 12:03 pm
This is great for the concepts – but for a newbie, i’m a little lost without an ab initio. i write web code, never use the command line, and am not sure if there is a software like subversion that is assumed to be in use?
brad — March 10, 2009 @ 9:18 am
@imissmyjuno: You’re welcome!
@brad: Thanks for the comment — I realize I forgot to mention the examples were for Subversion! (I’ll update that now). The key principles, pros and cons, and diagrams should apply to most traditional version control systems like Subversion, CVS or RCS.
Kalid — March 13, 2009 @ 1:47 am
Kalid,
Many thanks. I’m a small projects guy who has been wavering about using vcs for a while, and this tipped me toward using it.
Walter — March 14, 2009 @ 3:14 pm
@Walter: You’re welcome — hope it works out for you!
Kalid — March 14, 2009 @ 4:03 pm
most appreciated. u v got a great way of explaining concepts in a simple way. Thank u a lot n i wish u a lot of luck!
adi
adi — May 7, 2009 @ 6:59 am
Good article. Thanks.
Catherine Sea
http://www.scmsoftwareconfigurationmanagement.com/
Catherine — May 10, 2009 @ 11:56 pm
afasdfasdf
sfasdf — July 7, 2009 @ 4:14 am
Good article
Shyam — July 7, 2009 @ 4:35 am
Excellent article! Thanks for this fantastic article which explains(better! with clear diagrams, how VCS works … Done a bit of digging and SVN seems the way to go. Glad there’s a plugin for quanta plus since I use that for PHP. Again, thanks for an awesome article Kalid.
webCV — July 10, 2009 @ 12:48 am
@webCV: You’re welcome!
Kalid — July 10, 2009 @ 10:31 am
that was the most simplest of all
thx for sharing
Ranu Mandan — August 3, 2009 @ 7:28 am
@Ranu: Thanks!
Kalid — August 6, 2009 @ 7:46 pm
Thanks very much for sharing. I have been looking for an article like this
Ramesh — August 12, 2009 @ 2:05 pm
@Ramesh: You’re welcome!
Kalid — August 12, 2009 @ 2:09 pm
Kalid,
Can I reuse the pictures (copy) to our folks in a PPT or something??
Niks — August 17, 2009 @ 11:45 pm
@Niks: Sure thing, but please include a reference back to the site. Thanks!
Kalid — August 19, 2009 @ 8:53 pm
Sir, it was very useful to know the basics of how one of the largest software projects is organized.
Kavin — September 15, 2009 @ 11:01 pm
@Kavin: Glad you found it helpful!
Kalid — September 20, 2009 @ 12:25 am
Great stuff!now i fully get branching, and when to use RI or FI.
skmwenda — September 27, 2009 @ 7:54 am
@skmwenda: Thanks, glad it helped!
Kalid — September 27, 2009 @ 11:58 am
Awesome post….
Really nice and easy to learn Source Control Concepts from the scratch
LOve U buddy
S M Nabeel Dibaji — November 4, 2009 @ 10:43 pm
Great article for beginners. Thanks.
Deependra Solanky — November 4, 2009 @ 11:26 pm
@S M, @Deependra : Glad you liked it!
Kalid — November 5, 2009 @ 4:17 pm
Excellent! Thank you!
joy — December 17, 2009 @ 6:34 pm
@joy: You’re welcome!
Kalid — December 19, 2009 @ 2:04 am
Lovely guide. No prob in understanding at all.
Km — January 25, 2010 @ 4:47 am
thanks for the post, its really helpful
maverick — February 24, 2010 @ 12:17 am
Have a question? Know an explanation that caused your own a-ha moment? Write about it here.
广告联盟 — March 2, 2010 @ 10:31 pm
Amazingly well explained. I’m sending this to the non softare guys at work
Windows Linux Admin — March 19, 2010 @ 9:29 am
Excellent! Thank you!
シティゴールドカード — March 28, 2010 @ 9:33 pm
Woderful !! thank You !!!
sujith — May 24, 2010 @ 11:06 pm
That is really a good guide! Very easy to understand and helpful. I am having less fear to the version control things at least, haha. Thanks very much!
淼 — May 31, 2010 @ 6:48 am
@淼: Yoiu’re welcome, glad it helped!
Kalid — May 31, 2010 @ 10:30 pm
I was looking for a user guide to version control. This is really an excellent introduction.
Bernard — June 1, 2010 @ 11:08 am
@Bernard: Thanks!
Kalid — June 1, 2010 @ 12:30 pm
hi – I know this sounds like a tall order but does anyone know of a VCS that would deal with the entire origination process, please? (ie, pulling in all sorts of different source files – text, Word, EPSs, TIFs, jpegs – then through Quark/InDesign and through to PDF)
thanks
Rob
Rob Langley — June 24, 2010 @ 7:08 am
@Rob: I think your best bet would be to use VersionCue or some software designed just for the various Adobe formats — most generic VCS systems are optimized to working with plain text files.
Kalid — July 2, 2010 @ 10:37 pm
Great high-level SVN overview. Love the visuals!
Josh Colter — July 14, 2010 @ 11:39 am
Very informative and detailed note on VCS.
Is it an individual contribution or an organisations contribution ? whoever did it, thank you so much.
Ap
Appan — July 14, 2010 @ 11:59 am
@Appan: Thanks, glad you liked it! Yep, this was just a personal post, not part of an organization.
Kalid — July 14, 2010 @ 12:26 pm
Its cool, i have read some part and seems good
Raj — July 14, 2010 @ 10:29 pm
I’ve just started out to read the tutorial and I already want to tell you I felt in love with this whole new VCS stuff . Thanks for that! And of course, for this amazing tutorial.
m4niac — July 25, 2010 @ 12:32 pm
Absolutely Great. A credit to the author Kalid Azad. Very interesting and very easy to follow!
michael kenner — September 29, 2010 @ 1:48 am
@Michael: Thank you, glad it helped!
Kalid — October 8, 2010 @ 10:06 am
good article
ss — October 18, 2010 @ 2:29 pm
wow! i have never come across any read(specially in IT) which was so easy to understahnd.
i was LOL looking at the words like, blamestorming and monkeying.Absolutely loved it.
It truly is “better explained”.
keep up the good work.
Cheers!!
Anonymous — December 9, 2010 @ 1:10 pm
@Anonymous: Thanks! Yeah, there’s no reason guides have to be dull — nobody wants to read (or write) that .
Kalid — December 10, 2010 @ 2:21 am
WOW !! that was amazing and so simple indeed .. I’m a third year student in FCI and I have a presentation about VCS and I gotta tell you that ur article was more than helpful to me .. thanx alot .. great effort
Aya — December 17, 2010 @ 1:16 am
LOL looking at the words like, blamestorming and monkeying.Absolutely loved it.
西安二手房 — December 22, 2010 @ 11:37 pm
simply superb !
sakhunzai — December 28, 2010 @ 11:15 am
thanks a lot for this work, we will wait many from u
Anonymous — January 15, 2011 @ 2:51 am
Thanks you for explaining the basic principals it makes things more clear to me and will help me in fixing the way I set my VCS up and maintain it in the future.
Anonymous — March 1, 2011 @ 11:40 am
@Anonymous: You’re welcome!
Kalid — March 2, 2011 @ 3:03 pm
very illustrative content
Catherine — March 15, 2011 @ 10:36 pm
@Catherine: Thanks, glad you liked it.
Kalid — March 15, 2011 @ 11:29 pm
Hey ! this is a very good article. I had tried to understand version control, I didnt know where to start, luckily I found this. It’s simple, useful. Nice job!
Jorge Contreras — April 4, 2011 @ 7:42 am
Hi,
It was an awesome article on Version Control System. I have an interview on monday and less time to look around, but your information made my day. Its the best article I ever saw on VCS
Hats Off !
Pawankumar Jajara — April 9, 2011 @ 1:30 pm
@Pawankumar: Thanks!
Kalid — April 16, 2011 @ 6:53 pm
Wow, this article really gives me a fantastic idea of what version control is all about!!Great job!
Michelle — May 5, 2011 @ 8:59 pm
@Michelle: Thanks!
Kalid — May 5, 2011 @ 9:14 pm
ow, this article really gives me a fantastic idea of what version control is a
上海翻译公司 — May 21, 2011 @ 10:24 pm
betterexplained.com has been helping me and my college friends with our school projects.
sports management course — May 30, 2011 @ 1:44 am
Pretty kewl. Stands up to the name- BetterExplained
Mohnish Thallavajhula — June 4, 2011 @ 3:01 am
@Mohnish: Thanks .
Kalid — June 5, 2011 @ 8:43 pm
I actually wrote something very similar to this for my dissertation a few years ago. Great article, well done on explaining this a lot clearer than i could
Denim Geek — July 5, 2011 @ 5:49 am
@Denim Geek: Appreciate the comment!
Kalid — July 18, 2011 @ 12:19 pm
hello people i fell really helpful with this data provided…..actually VCS is my research topic so..i was just thinking that if u could send me some more contents over VCS…it will be very very helpful to me …bdw thanx a lot kalid…:)
rosy — August 10, 2011 @ 10:34 pm
good stuff mate..!!!!
raj — September 4, 2011 @ 10:34 pm
RSS feed for comments on this post. TrackBack URI
Leave a comment
Have a question? Know an explanation that caused your own a-ha moment? Write about it here.
Name
E-mail
URL
Your Comment (HTML a and code tags allowed)
Subscribe (RSS or Email)
Get new articles by email:
Get the Math, BetterExplained ebook for clear insights into key math concepts.
Get the ebook
About (Contact Kalid)
Learning shouldn't hurt. Let's share the insights that made difficult ideas click. Read more...
Popular | All | Random Post
Easy Permutations and Combinations
An Intuitive Guide To Exponential Functions & e
How To Optimize Your Site With GZIP Compression
A Visual Guide to Version Control
A Visual, Intuitive Guide to Imaginary Numbers
A Gentle Introduction To Learning Calculus
Demystifying the Natural Logarithm (ln)
Understanding Big and Little Endian Byte Order
Intro to Distributed Version Control (Illustrated)
How to Develop a Mindset for Math
How To Measure Any Distance With The Pythagorean Theorem
Techniques for adding the numbers 1 to 100
Categories
Business
General
Guides
Math
Calculus
Vector Calculus
Observations
Personal Development
Programming
Web
LIKE IT? TRY ALL ARTICLES, RSS FEED OR EMAIL SUBSCRIPTION | IDEA OR SUGGESTION? CONTACT ME
COPYRIGHT © 2011 KALID AZADversion control subversion svn tutorial versioncontrol guide reference programming howto
-
16 Aug 11
-
12 Jul 11
-
30 Jun 11
-
18 Jun 11
-
13 Jun 11
-
04 Jun 11
-
24 May 11
-
17 May 11
Michelle A. Hoyle"Version Control (aka Revision Control aka Source Control) lets you track your files over time. Why do you care? So when you mess up you can easily get back to a previous working version."
An easy-to-understand explanation of version control with lots of pictures to help illustrate the basic ideas. Uses Subversion instead of CVS but don't let that stop you. They're pretty similar.tutorial versioning opensource how-to programming tt381 subversion
-
16 May 11
-
26 Apr 11
Fernando lopezGreat resource to pass to people that are not familiar with Version Control and they need to understand what the whole thing is about.
-
14 Apr 11
-
01 Apr 11
-
22 Mar 11
-
03 Mar 11
-
02 Mar 11
-
08 Feb 11
-
02 Feb 11
-
26 Jan 11
-
23 Jan 11
-
07 Jan 11
-
23 Dec 10
-
19 Dec 10
-
27 Oct 10
-
19 Oct 10
-
13 Oct 10
-
24 Sep 10
-
02 Sep 10
Alejandro GarcíaVersion Control (aka Revision Control aka Source Control) lets you track your files over time. Why do you care? So when you mess up you can easily get back to a previous working version.
subversion svn versioncontrol tutorial programming reference guide howto
-
30 Aug 10
-
24 Aug 10
-
12 Aug 10
-
26 Jul 10
-
15 Jul 10
-
22 Jun 10
-
16 Jun 10
-
14 Jun 10
-
07 Jun 10
-
29 Apr 10
-
02 Apr 10
dickklaverVersion Control (aka Revision Control aka Source Control) lets you track your files over time. Why do you care? So when you mess up you can easily get back
version control subversion tutorial guide versioncontrol programming howto
-
01 Apr 10
-
29 Mar 10
-
23 Mar 10
-
11 Mar 10
-
04 Mar 10
Lodovico KetjapoVersion Control (aka Revision Control aka Source Control) lets you track your files over time. Why do you care? So when you mess up you can easily get back to a previous working version.
-
01 Mar 10
-
17 Feb 10
-
12 Feb 10
-
10 Jan 10
-
09 Jan 10
arghya dasguptausing powerpoint 2007 good graphics
-
Santo SubitoUna guida visuale al controllo di versione
-
30 Dec 09
-
25 Dec 09
-
22 Dec 09
-
18 Dec 09
-
14 Dec 09
-
02 Dec 09
Thanakrit WongyuedVersion Control (aka Revision Control aka Source Control) lets you track your files over time. Why do you care? So when you mess up you can easily get back
-
22 Nov 09
-
18 Nov 09
-
10 Nov 09
-
03 Nov 09
-
26 Oct 09
-
03 Oct 09
-
29 Sep 09
-
08 Sep 09
-
04 Sep 09
-
03 Sep 09
Shawn Skriver<wayita> IcePic: http://betterexplained.com/articles/a-visual-guide-to-version-control/
-
02 Sep 09
-
31 Aug 09
-
28 Aug 09
-
27 Aug 09
-
24 Aug 09
-
23 Aug 09
-
18 Aug 09
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.