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

Re: checkout-cache -f: a better way?

From
Junio C Hamano <junkio@cox.net>
Date
May 20, 2005, 23:39 UTC
Message-ID
<7vvf5dqxfq.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<428E73B9.1080907@pobox.com>
>>>>> "JG" == Jeff Garzik <jgarzik@pobox.com> writes:
JG> git-checkout-cache -f writes out every file, even if it exists, correct?

No, that's not correct. To translate my prose, you would want this:

    git-read-tree -m HEAD && git-checkout-cache -q -f -u -a

(notice that I do not have git-update-cache --refresh after that).

Previous: Jeff GarzikNext: Jeff Garzik
Message 4 of 11 in “checkout-cache -f: a better way?”
  1. Jeff GarzikMay 20, 2005
  2. Junio C HamanoMay 20, 2005
  3. Jeff GarzikMay 20, 2005
  4. Junio C HamanoMay 20, 2005
  5. Jeff GarzikMay 20, 2005
  6. Linus TorvaldsMay 21, 2005
  7. Jeff GarzikMay 21, 2005
  8. Linus TorvaldsMay 20, 2005
  9. Linus TorvaldsMay 20, 2005
  10. Jeff GarzikMay 20, 2005
  11. Junio C HamanoMay 20, 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.