Re: checkout-cache -f: a better way?
- From
- Jeff Garzik <jgarzik@pobox.com>
- Date
- May 20, 2005, 23:33 UTC
- Message-ID
- <428E73B9.1080907@pobox.com>
- In-Reply-To
- <7vacmpsetb.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
Show 23 quoted lines
>>>>>>"JG" == Jeff Garzik <jgarzik@pobox.com> writes: > > > JG> Being a weirdo, I don't use cogito for kernel development, just git > JG> itself. > > My customer, in other words ;-). > > JG> git-read-tree $(cat .git/HEAD) && \ > JG> git-checkout-cache -q -f -a && \ > JG> git-update-cache --refresh > > I have to check checkout-cache.c, but assuming that you start > from an already populated work tree with a valid cache when you > do the git-read-tree at the third line from the last, using > "git-read-tree -m HEAD" (you do not need to say $(cat .git/HEAD) > in the modern git anymore) would be a good place to start. > > Also the modern git-checkout-cache has a '-u' option and with it > you should not need 'git-update-cache --refresh' after that. > > Let me know if you have any problems. Single tree '-m' is what > Linus did and '-u' option to git-checkout-cache is mine.
Pardon my ignorance (I'm slow :)), but how do those changes address the fact that git-checkout-cache appears to checkout the entire kernel tree (over 100MB of writes) when using '-f' ?
git-checkout-cache -f writes out every file, even if it exists, correct?
Jeff