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

Re: first para of man gitignore should refer to 'git rm --cached'

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Nov 9, 2010, 19:29 UTC
Message-ID
<20101109192913.GA21320@burratino>
In-Reply-To
<AANLkTimwNtih94GENv=RqTCYtTWC7koLV_=WTX-B3MDu@mail.gmail.com>
Sitaram Chamarty wrote:
> Perhaps it's the difference between the folks that come to #git and
> those that come to the mailing list.
> 
> But case closed I guess...

Case closed? I thought you were suggesting an enhancement to the manual page, to answer the following question (frequently asked or not):

	If git is already tracking a file, how can I tell git
	it is not supposed to be tracked any more?
And perhaps a bonus question:
	What will happen when I switch between revisions in
	which the file is tracked and not tracked?

I think at least an EXAMPLES section explaining this would be would be nice.

Previous: Sitaram Chamarty
Message 6 of 6 in “first para of man gitignore should refer to 'git rm --cached'”
  1. Sitaram ChamartyNov 7, 2010
  2. Ramkumar RamachandraNov 7, 2010
  3. Sitaram ChamartyNov 8, 2010
  4. Junio C HamanoNov 8, 2010
  5. Sitaram ChamartyNov 9, 2010
  6. Jonathan NiederNov 9, 2010

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.