Thread (3 messages) flat view 3 messages, 3 authors, 2016-06-15

Re: [PATCH 1/2] Documentation/git-checkout.txt: clarify usage

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:55:32

Possibly related (same subject, not in this thread)

"Philip Oakley" [off-list ref] writes:
From: "Junio C Hamano" <redacted> Sent: Monday, December 17,
quoted
This is to "check out the branch" ;-)
...
From a user perspective it's better to refer to the working directory
first rather than the internal mechanics.

   Prepare to work on <branch>, by updating the files in the
   working tree and index to the branch's previous content, and
   pointing HEAD to it.
I agree that the mention of "pointing HEAD to" may be better to be
rephrased in the user facing terms.

Because the primary purpose of "git checkout <branch>" is to "check
out the branch so that further work is done on that branch", that
aspect of the behaviour should be mentioned first.  Updating of the
working tree files and the index is the implemenation detail of
starting to work on that branch.

So your suggestion is going backwards, I'd have to say.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help