public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox•net>
To: "Nguyen Thai Ngoc Duy" <pclouds@gmail•com>
Cc: "Andreas Ericsson" <ae@op5•se>, git@vger•kernel.org
Subject: Re: Restore a single file in the index back to HEAD
Date: Wed, 01 Nov 2006 00:07:16 -0800	[thread overview]
Message-ID: <7vpsc78ua3.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <fcaeb9bf0610312358g1176e4d8q8962b08c2e8ff2c6@mail.gmail.com> (Nguyen Thai Ngoc Duy's message of "Wed, 1 Nov 2006 14:58:54 +0700")

"Nguyen Thai Ngoc Duy" <pclouds@gmail•com> writes:

> On 10/27/06, Junio C Hamano <junkio@cox•net> wrote:
>> On the other hand, I designed --index-info to be compatible with
>> ls-tree output (it is not an accident, it was designed).  In
>>
>>         git ls-tree HEAD frotz | git update-index --index-info
>>
>> "frotz" part does not have to be the exact path but can be a
>> directory name.  It means "revert everything in this directory".
>>
>> This is quite heavy-handed and you would probably want to run
>> update-index --refresh afterwards.
>
> I would prefer "git update-index --reset frotz" or "git checkout
> --index HEAD frotz". git ls-tree|git update-index is too cryptic for
> me and too long for my fingers.

Then perhaps you can use "git checkout HEAD frotz", which is the
simplest?


  reply	other threads:[~2006-11-01  8:07 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 [this message]
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 ` [PATCH] Added description for inverting git-update-index using --index-info Andy Parkins

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=7vpsc78ua3.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox$(echo .)net \
    --cc=ae@op5$(echo .)se \
    --cc=git@vger$(echo .)kernel.org \
    --cc=pclouds@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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