Read Anywhere and on Any Device!

Special Offer | $0.00

Join Today And Start a 30-Day Free Trial and Get Exclusive Member Benefits to Access Millions Books for Free!

Read Anywhere and on Any Device!

  • Download on iOS
  • Download on Android
  • Download on iOS

Source Control HOWTO

Erik Sink
4.9/5 (34977 ratings)
Description:An introduction to source control using "centralized" version control tools such as SourceGear Vault.Chapter 0: IntroductionOur universities don't teach people how to do source control. Our employers don't teach people how to do source control. SCM tool vendors don't teach people how to do source control. We need some materials that explain how source control is done. My goal for this series of articles is to create a comprehensive guide to help meet this need.Chapter 1: BasicsOur discussion of source control must begin by defining the basic terms and describing the basic operations.Chapter 2: CheckinsIn this chapter, I will explore the various situations wherein a repository is modified, starting with the simplest case of a single developer making a change to a single file.Chapter 3: File MergeMany software teams have discovered that the tradeoff here is worth the trouble. Concurrent development can bring substantial gains in the productivity of a team. The extra effort to deal with merge situations is usually a small price to pay.Chapter 4: RepositoriesA file system is two-dimensional: its space is defined by directories and files. In contrast, a repository is three-dimensional: it exists in a continuum defined by directories, files and time. An SCM repository contains every version of your source code that has ever existed. The additional dimension creates some rather interesting challenges in the architecture of a repository and the decisions about how it manages data.Chapter 5: Working FoldersThe repository is the official archive of our work. We treat our repository with great respect. In contrast, we treat our working folder with very little regard. It exists for the purpose of being abused. Our working folder starts out worthless, nothing more than a copy of the repository. If it is destroyed, we have lost nothing, so we run risky experiments which endanger its life.Chapter 6: HistoryThere is nothing endearing about a development team that can't find something when they need it. A good SCM tool must do more than just keep every version of everything. It must also provide ways of searching and viewing and sorting and organizing and finding all that stuff.Chapter 7: BranchesNelly has a friend who has a cousin with a neighbor who knows somebody whose life completely fell apart after they tried using the branch and merge features of their source control tool. So Nelly refuses to use branching at all.Chapter 8: Merge BranchesSuccessfully using the branching and merging features of your source control tool is first a matter of attitude on the part of the developer. No matter how much help the source control tool provides, it is not as smart as you are. You are responsible for doing the merge. Think of the tool as a tool, not as a consultant.Chapter 9: Source Control Integration with IDEsJust as a spice rack belongs near the stove, source control should always be available where the developer is working.We have made it easy for you to find a PDF Ebooks without any digging. And by having access to our ebooks online or by storing it on your computer, you have convenient answers with Source Control HOWTO. To get started finding Source Control HOWTO, you are right to find our website which has a comprehensive collection of manuals listed.
Our library is the biggest of these that have literally hundreds of thousands of different products represented.
Pages
Format
PDF, EPUB & Kindle Edition
Publisher
Release
2006
ISBN

Source Control HOWTO

Erik Sink
4.4/5 (1290744 ratings)
Description: An introduction to source control using "centralized" version control tools such as SourceGear Vault.Chapter 0: IntroductionOur universities don't teach people how to do source control. Our employers don't teach people how to do source control. SCM tool vendors don't teach people how to do source control. We need some materials that explain how source control is done. My goal for this series of articles is to create a comprehensive guide to help meet this need.Chapter 1: BasicsOur discussion of source control must begin by defining the basic terms and describing the basic operations.Chapter 2: CheckinsIn this chapter, I will explore the various situations wherein a repository is modified, starting with the simplest case of a single developer making a change to a single file.Chapter 3: File MergeMany software teams have discovered that the tradeoff here is worth the trouble. Concurrent development can bring substantial gains in the productivity of a team. The extra effort to deal with merge situations is usually a small price to pay.Chapter 4: RepositoriesA file system is two-dimensional: its space is defined by directories and files. In contrast, a repository is three-dimensional: it exists in a continuum defined by directories, files and time. An SCM repository contains every version of your source code that has ever existed. The additional dimension creates some rather interesting challenges in the architecture of a repository and the decisions about how it manages data.Chapter 5: Working FoldersThe repository is the official archive of our work. We treat our repository with great respect. In contrast, we treat our working folder with very little regard. It exists for the purpose of being abused. Our working folder starts out worthless, nothing more than a copy of the repository. If it is destroyed, we have lost nothing, so we run risky experiments which endanger its life.Chapter 6: HistoryThere is nothing endearing about a development team that can't find something when they need it. A good SCM tool must do more than just keep every version of everything. It must also provide ways of searching and viewing and sorting and organizing and finding all that stuff.Chapter 7: BranchesNelly has a friend who has a cousin with a neighbor who knows somebody whose life completely fell apart after they tried using the branch and merge features of their source control tool. So Nelly refuses to use branching at all.Chapter 8: Merge BranchesSuccessfully using the branching and merging features of your source control tool is first a matter of attitude on the part of the developer. No matter how much help the source control tool provides, it is not as smart as you are. You are responsible for doing the merge. Think of the tool as a tool, not as a consultant.Chapter 9: Source Control Integration with IDEsJust as a spice rack belongs near the stove, source control should always be available where the developer is working.We have made it easy for you to find a PDF Ebooks without any digging. And by having access to our ebooks online or by storing it on your computer, you have convenient answers with Source Control HOWTO. To get started finding Source Control HOWTO, you are right to find our website which has a comprehensive collection of manuals listed.
Our library is the biggest of these that have literally hundreds of thousands of different products represented.
Pages
Format
PDF, EPUB & Kindle Edition
Publisher
Release
2006
ISBN
loader