From: Pieter de Bie <pdebie@ai.rug.nl>
To: gitster@pobox.com, git@vger.kernel.org
Cc: Pieter de Bie <pdebie@ai.rug.nl>
Subject: [PATCH 2/2] Documentation: Add a usage case of git-reset with path
Date: Sat, 16 Feb 2008 17:48:46 +0100 [thread overview]
Message-ID: <1203180526-12020-2-git-send-email-pdebie@ai.rug.nl> (raw)
In-Reply-To: <1203180526-12020-1-git-send-email-pdebie@ai.rug.nl>
Signed-off-by: Pieter de Bie <pdebie@ai.rug.nl>
---
Documentation/git-reset.txt | 17 +++++++++++++++++
1 files changed, 17 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-reset.txt b/Documentation/git-reset.txt
index 2b24641..39a9d64 100644
--- a/Documentation/git-reset.txt
+++ b/Documentation/git-reset.txt
@@ -176,6 +176,23 @@ $ git reset <3>
committed as 'snapshot WIP'. This updates the index to show your
WIP files as uncommitted.
+Reset a single file in the index::
++
+Suppose you have added a file to your index, but later decide you do not
+want to add it to your commit. You can remove the file from the index
+while keeping your changes with git reset.
++
+------------
+$ git reset -- frotz.c <1>
+$ git commit -m "Commit files in index" <2>
+$ git add frotz.c <3>
+------------
++
+<1> This removes the file from the index while keeping it in the working
+ directory.
+<2> This commits all other changes in the index.
+<3> Adds the file to the index again.
+
Author
------
Written by Junio C Hamano <junkio@cox.net> and Linus Torvalds <torvalds@osdl.org>
--
1.5.4.3.gb183
next prev parent reply other threads:[~2008-02-16 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 16:48 [PATCH 1/2] Documentation: Remove deprecated --mixed option in git-reset synopsis Pieter de Bie
2008-02-16 16:48 ` Pieter de Bie [this message]
2008-02-16 18:40 ` [PATCH 2/2] Documentation: Add a usage case of git-reset with path Junio C Hamano
2008-02-16 19:15 ` [PATCH 1/2] Documentation: Remove deprecated --mixed option in git-reset synopsis Junio C Hamano
2008-02-16 19:17 ` Pieter de Bie
2008-02-16 20:10 ` Junio C Hamano
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=1203180526-12020-2-git-send-email-pdebie@ai.rug.nl \
--to=pdebie@ai.rug.nl \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).