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

Re: git rm --cached and pull semantics

From
Llist@phuk.ath.cx <list@phuk.ath.cx>
Date
Jan 18, 2010, 02:31 UTC
Message-ID
<4B53C7FF.7060604@phuk.ath.cx>
In-Reply-To
<86my0c5l9s.fsf@blue.stonehenge.com>
On 01/18/2010 01:06 AM, Randal L. Schwartz wrote:
Show 10 quoted lines
> The real WTF here is that you are using a workdir as your live dir.
>
> If you treat git as a *source* manager like it is, you'd also have an
> installer that would copy the resulting files into their live locations,
> and could be edited to either leave that newly untracked file alone,
> or deliberately remove it.
>
> Use git as intended, and you get no problems.
>
>

Hm. Good point. I'll try to put that into some post-pull hook and see how it works out. Thanks for the help.

Previous: Randal L. Schwartz
Message 5 of 5 in “git rm --cached and pull semantics”
  1. list@phuk.ath.cxJan 16, 2010
  2. Matthieu MoyJan 17, 2010
  3. list@phuk.ath.cxJan 17, 2010
  4. Randal L. SchwartzJan 18, 2010
  5. list@phuk.ath.cxJan 18, 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.