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

Re: understanding index

From
Alex Riesen <raa.lkml@gmail.com>
Date
Jan 31, 2009, 14:45 UTC
Message-ID
<81b0412b0901310645t4307f67vf546e9c1c8c07701@mail.gmail.com>
In-Reply-To
<adf1fd3d0901310409y28dc493ak358749e0c29154cc@mail.gmail.com>
2009/1/31 Santi Béjar <santi@agolina.net>:
Show 10 quoted lines
> 2009/1/31 Nicolas Sebrecht <nicolas.s-dev@laposte.net>:
>> I'm having some understanding trouble with git index. As I understand,
>> 'git rm --cached' is not strictly the opposite of 'git add'. It's a
>> little embarrassing in this particular case : what if you want to
>> commit and did a wrong 'git add -u' command ?
>>
> So to not commit foo at all:
>
> git reset HEAD foo
>
Or look at git gui, which allows you to select the not-to-commit parts visually
Previous: Santi BéjarNext: Nicolas Sebrecht
Message 3 of 7 in “understanding index”
  1. Nicolas SebrechtJan 31, 2009
  2. Santi BéjarJan 31, 2009
  3. Alex RiesenJan 31, 2009
  4. Nicolas SebrechtJan 31, 2009
  5. Santi BéjarJan 31, 2009
  6. Nicolas SebrechtJan 31, 2009
  7. Björn SteinbrinkJan 31, 2009

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.