How does --assume-unchanged impact git-p4?
- From
- Corey Thompson <cmtptr@gmail.com>
- Date
- Mar 9, 2012, 15:58 UTC
- Message-ID
- <20120309155848.GA5998@jerec>
Hello,
My workplace uses Perforce, so I've started using git-p4 to interface with it. Some of the files included in our depot are cached pre-compiled binaries which do a great deal of damage to git's performance, so after some research I found that I can "git update-index --assume-unchanged" on these files. This is great except that now I'm worried that this might prevent git-p4 from doing its thing when someone else updates these files.
So am I going to miss updates to our cached binaries using this method? Is there a better method I should be using in this scenario?
Thanks, Corey