From 4c52aa1b4ea7e46f83985814598044fad9c4eb1d Mon Sep 17 00:00:00 2001 From: Ben Lynn Date: Tue, 5 Aug 2008 21:22:40 -0700 Subject: [PATCH] Minor corrections. --- branch.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/branch.txt b/branch.txt index 65a4622..b4cf9e6 100644 --- a/branch.txt +++ b/branch.txt @@ -61,9 +61,9 @@ and commit before switching back to the master branch. Whenever you want to retu $ git checkout dirty -We touched upon this command in an earlier chapter, when discussing loading old states. Now we can describe what happens when you load an old state using the checkout command: the files change to the requested state, but we must leave the master branch. Any commits made from now on take your files down a different road. +We touched upon this command in an earlier chapter, when discussing loading old states. At last we can tell the whole story: the files change to the requested state, but we must leave the master branch. Any commits made from now on take your files down a different road, which can be named later. -Hence after checking out an old state, Git automatically puts you in a new, unnamed branch, which can be named and saved with *git checkout -b*. +In other words, after checking out an old state, Git automatically puts you in a new, unnamed branch, which can be named and saved with *git checkout -b*. === Quick Fixes === @@ -119,7 +119,7 @@ It's easy to extend this trick for any number of parts. === Reorganizing a Medley === -Perhaps you like to work on all aspects of a project in the same branch. You want to keep works-in-progress to yourself and want others to see your commits only when they have been neatly organized. Then after cloning: +Perhaps you like to work on all aspects of a project in the same branch. You want to keep works-in-progress to yourself and want others to see your commits only when they have been neatly organized. Make a couple of clones: $ git checkout -b sanitized $ git checkout -b medley -- 2.11.4.GIT