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

Re: index manipulation -- how?

From
Junio C Hamano <junkio@cox.net>
Date
Nov 22, 2005, 07:05 UTC
Message-ID
<7vbr0dgo1f.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20051122062048.8891.qmail@web31805.mail.mud.yahoo.com>
Luben Tuikov <ltuikov@yahoo.com> writes:
> (There is a very similar construct in git-checkout.sh.
> So if you apply the patch below, please make sure
> git-checkout.sh doesn't break.)
Thanks.
Show 5 quoted lines
> Question: so in effect, more generally:
>   git checkout <tree-ish> <file>
>
> would do the right thing: update index and the working
> tree as the file <file> looked as it was at <tree-ish>?

Yes that is correct. Also by omitting <tree-ish> you can checkout from the index.

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>.

Previous: Luben TuikovNext: Luben Tuikov
Message 6 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.