# [PATCH] Rewrite synopsis to clarify the two primary uses of git-checkout. 2 messages from 2006-03-18 to 2006-03-18. Participants: Jon Loeliger, Junio C Hamano. Thread: https://gitlist.dev/t/3665 ## Jon Loeliger, 2006-03-18 00:26 Subject: [PATCH] Rewrite synopsis to clarify the two primary uses of git-checkout. Message-ID: URL: https://gitlist.dev/e/E1FKPGb-00062a-QC%40jdl.com ``` Fix a few typo/grammar problems. Signed-off-by: Jon Loeliger --- Documentation/git-checkout.txt | 23 +++++++++++++---------- 1 files changed, 13 insertions(+), 10 deletions(-) 3a8c8dc1832fcffe58cdc4894959f67d91c6a924 diff --git a/Documentation/git-checkout.txt b/Documentation/git-checkout.txt index 556e733..dc821bb 100644 --- a/Documentation/git-checkout.txt +++ b/Documentation/git-checkout.txt @@ -7,15 +7,18 @@ git-checkout - Checkout and switch to a SYNOPSIS -------- -'git-checkout' [-f] [-b ] [-m] [] [...] +[verse] +'git-checkout' [-f] [-b ] [-m] [] +'git-checkout' [-m] [] ... DESCRIPTION ----------- -When are not given, this command switches branches, by +When are not given, this command switches branches by updating the index and working tree to reflect the specified branch, , and updating HEAD to be or, if -specified, . +specified, . Using -b will cause to +be created. When are given, this command does *not* switch branches. It updates the named paths in the working tree from @@ -29,17 +32,17 @@ given paths before updating the working OPTIONS ------- -f:: - Force an re-read of everything. + Force a re-read of everything. -b:: Create a new branch and start it at . -m:: - If you have local modifications to a file that is - different between the current branch and the branch you - are switching to, the command refuses to switch - branches, to preserve your modifications in context. - With this option, a three-way merge between the current + If you have local modifications to one or more files that + are different between the current branch and the branch to + which you are switching, the command refuses to switch + branches in order to preserve your modifications in context. + However, with this option, a three-way merge between the current branch, your working tree contents, and the new branch is done, and you will be on the new branch. + @@ -82,7 +85,7 @@ $ git checkout -- hello.c ------------ . After working in a wrong branch, switching to the correct -branch you would want to is done with: +branch would be done using: + ------------ $ git checkout mytopic -- 1.2.4.gdd7be ``` ## Junio C Hamano, 2006-03-18 07:11 Subject: Re: [PATCH] Rewrite synopsis to clarify the two primary uses of git-checkout. Message-ID: <7v7j6sz0qb.fsf@assigned-by-dhcp.cox.net> URL: https://gitlist.dev/e/7v7j6sz0qb.fsf%40assigned-by-dhcp.cox.net In-Reply-To: ``` All 7 look good. Thanks. ```