From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH] Added description for inverting git-update-index using --index-info
Date: Fri, 27 Oct 2006 10:03:03 +0100 [thread overview]
Message-ID: <200610271003.03308.andyparkins@gmail.com> (raw)
In-Reply-To: <200610261641.11239.andyparkins@gmail.com>
I wanted to restore a single file from HEAD back to the index; Shawn Pearce
gave me the answer. git-ls-tree piped to git-update-index --index-info.
This patch adds that answer to the git-update-index documentation.
Signed-off-by: Andy Parkins <andyparkins@gmail.com>
---
Documentation/git-update-index.txt | 18 ++++++++++++++++++
1 files changed, 18 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-update-index.txt b/Documentation/git-update-index.txt
index 41bb7e1..5adf717 100644
--- a/Documentation/git-update-index.txt
+++ b/Documentation/git-update-index.txt
@@ -215,6 +215,24 @@ $ git ls-files -s
100755 8a1218a1024a212bb3db30becd860315f9f3ac52 2 frotz
------------
+One particular use of --index-info is to reverse the effect of
+"git-update-index frotz":
+
+------------
+git ls-tree HEAD frotz | git update-index --index-info
+------------
+
+This makes the index hold the file frotz from HEAD rather than from the
+working copy. Similarly:
+
+------------
+git ls-tree -r HEAD | git update-index --index-info
+------------
+
+Will undo everything except "git add" from the index, as
+"git-ls-tree -r" lists everything in the last commit.
+
+
Using "assume unchanged" bit
----------------------------
--
1.4.3.3.g5bca6
prev parent reply other threads:[~2006-10-27 9:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 15:41 Restore a single file in the index back to HEAD Andy Parkins
2006-10-26 15:42 ` Alex Riesen
2006-10-27 7:27 ` Andy Parkins
2006-10-27 7:38 ` Shawn Pearce
2006-10-27 8:01 ` Andy Parkins
2006-10-27 8:08 ` Andreas Ericsson
2006-10-27 8:15 ` Shawn Pearce
2006-10-27 9:45 ` Alex Riesen
2006-10-27 9:50 ` Andreas Ericsson
2006-10-27 10:02 ` Junio C Hamano
2006-10-27 17:45 ` Luben Tuikov
2006-11-01 7:58 ` Nguyen Thai Ngoc Duy
2006-11-01 8:07 ` Junio C Hamano
2006-11-01 8:34 ` Junio C Hamano
2006-11-01 9:09 ` Nguyen Thai Ngoc Duy
2006-11-01 11:22 ` Jakub Narebski
2006-11-01 9:38 ` Jakub Narebski
2006-11-01 8:39 ` Andy Parkins
2006-11-01 8:56 ` Junio C Hamano
2006-11-01 9:53 ` Andy Parkins
2006-11-01 18:28 ` Junio C Hamano
2006-11-01 20:29 ` Andy Parkins
2006-11-01 20:49 ` Junio C Hamano
2006-11-01 21:18 ` Andy Parkins
2006-11-01 22:08 ` Junio C Hamano
2006-11-01 23:09 ` Andy Parkins
2006-11-01 23:39 ` Junio C Hamano
2006-11-02 8:44 ` Andy Parkins
2006-11-01 22:27 ` Robin Rosenberg
2006-11-02 12:47 ` Salikh Zakirov
2006-10-27 9:03 ` Andy Parkins [this message]
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=200610271003.03308.andyparkins@gmail.com \
--to=andyparkins@gmail.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.