git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: index manipulation -- how?

From
LTLuben Tuikov <ltuikov@yahoo.com>
Date
Nov 22, 2005, 07:35 UTC
Message-ID
<20051122073538.4708.qmail@web31806.mail.mud.yahoo.com>
In-Reply-To
<7vbr0dgo1f.fsf@assigned-by-dhcp.cox.net>
--- Junio C Hamano <junkio@cox.net> wrote:
Show 5 quoted lines
> 
> I thought what you originally wanted to do was revert only index
> without losing your changes from the working tree, so just to
> make sure, the above does _not_ do it --- the named file in the
> working tree is also reverted to the one from <tree-ish>.
Exactly what I want.
Thanks,
   Luben
P.S. I figured this one out in three stages:
Since checked out files are in rw- mode, but unchecked
files simply do not exist, first I want to "revert"
a changed file in the working tree -- this one is easy.
Then the second stage is if also the index is updated
(but no commit), and the last stage is if also
there is a commit, for which I think I know what to use.
Previous: Junio C Hamano
Message 7 of 7 in “index manipulation -- how?”
  1. Luben TuikovNov 22, 2005
  2. Linus TorvaldsNov 22, 2005
  3. Junio C HamanoNov 22, 2005
  4. Junio C HamanoNov 22, 2005
  5. Luben TuikovNov 22, 2005
  6. Junio C HamanoNov 22, 2005
  7. Luben TuikovNov 22, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.