How does --assume-unchanged impact git-p4?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]