Skip to content

Commit

Permalink
Merge pull request progit#126 from pcasaretto/master
Browse files Browse the repository at this point in the history
Corrected a typo in en/03-git-branching/01-chapter3.markdown
  • Loading branch information
schacon committed Dec 8, 2011
2 parents 4e8fa5c + 89d4b42 commit a906fc0
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion en/03-git-branching/01-chapter3.markdown
Expand Up @@ -2,7 +2,7 @@

Nearly every VCS has some form of branching support. Branching means you diverge from the main line of development and continue to do work without messing with that main line. In many VCS tools, this is a somewhat expensive process, often requiring you to create a new copy of your source code directory, which can take a long time for large projects.

Some people refer to the branching model in Git as its “killer feature,” and it certainly sets Git apart in the VCS community. Why is it so special? The way Git branches is incredibly lightweight, making branching operations nearly instantaneous and switching back and forth between branches generally just as fast. Unlike many other VCSs, Git encourages a workflow that branches and merges often, even multiple times in a day. Understanding and mastering this feature gives you a powerful and unique tool and can literally change the way that you develop.
Some people refer to the branching model in Git as its “killer feature” , and it certainly sets Git apart in the VCS community. Why is it so special? The way Git branches is incredibly lightweight, making branching operations nearly instantaneous and switching back and forth between branches generally just as fast. Unlike many other VCSs, Git encourages a workflow that branches and merges often, even multiple times in a day. Understanding and mastering this feature gives you a powerful and unique tool and can literally change the way that you develop.

## What a Branch Is ##

Expand Down

0 comments on commit a906fc0

Please sign in to comment.