From: "Torsten Bögershausen" <tboegi@web.de>
To: git@vger.kernel.org
Cc: tboegi@web.de, eda@waniasset.com
Subject: [PATCH] git-checkout.txt: Document "git checkout <pathspec>" better
Date: Mon, 08 Jun 2015 22:21:28 +0200 [thread overview]
Message-ID: <5575F948.4060400@web.de> (raw)
git checkout <pathspec> can be used to revert changes in the working tree.
Signed-off-by: Torsten Bögershausen <tboegi@web.de>
---
My first attempt to improve the documentation
Documentation/git-checkout.txt | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-checkout.txt b/Documentation/git-checkout.txt
index d263a56..8cd018a 100644
--- a/Documentation/git-checkout.txt
+++ b/Documentation/git-checkout.txt
@@ -3,7 +3,7 @@ git-checkout(1)
NAME
----
-git-checkout - Checkout a branch or paths to the working tree
+git-checkout - Switch branches or reverts changes in the working tree
SYNOPSIS
--------
@@ -83,7 +83,8 @@ Omitting <branch> detaches HEAD at the tip of the current branch.
When <paths> or `--patch` are given, 'git checkout' does *not*
switch branches. It updates the named paths in the working tree
from the index file or from a named <tree-ish> (most often a
- commit). In this case, the `-b` and `--track` options are
+ commit). Changes in files are discarded and deleted files are
+ restored. In this case, the `-b` and `--track` options are
meaningless and giving either of them results in an error. The
<tree-ish> argument can be used to specify a specific tree-ish
(i.e. commit, tag or tree) to update the index for the given
--
2.2.0.rc1.790.ge19fcd2
next reply other threads:[~2015-06-08 20:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 20:21 Torsten Bögershausen [this message]
2015-06-10 15:05 ` [PATCH] git-checkout.txt: Document "git checkout <pathspec>" better Junio C Hamano
2015-06-10 15:11 ` Ed Avis
2015-06-10 16:38 ` Junio C Hamano
2015-06-11 10:24 ` [PATCH] git-checkout.txt: Document Ed Avis
2015-06-10 18:27 ` [PATCH] git-checkout.txt: Document "git checkout <pathspec>" better Torsten Bögershausen
2015-06-11 14:47 ` Junio C Hamano
2015-06-11 14:52 ` Ed Avis
2015-06-11 18:23 ` Junio C Hamano
2015-06-12 4:49 ` Scott Schmit
2015-06-12 16:24 ` Junio C Hamano
2015-06-12 20:41 ` Torsten Bögershausen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5575F948.4060400@web.de \
--to=tboegi@web.de \
--cc=eda@waniasset.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.