{"thread":{"id":"29896","subject":"How does --assume-unchanged impact git-p4?","startedAt":"2012-03-09T15:58:48Z","lastAt":"2012-03-25T13:55:48Z","messageCount":2,"participants":["Corey Thompson","Pete Wyckoff"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"186568","messageId":"20120309155848.GA5998@jerec","threadId":"29896","inReplyTo":null,"subject":"How does --assume-unchanged impact git-p4?","fromName":"Corey Thompson","fromEmail":"cmtptr@gmail.com","sentAt":"2012-03-09T15:58:48Z","receivedAt":"2012-03-09T15:58:48Z","isPatch":false,"sender":{"key":"cmtptr@gmail.com","avatar":null},"body":"Hello,\n\nMy workplace uses Perforce, so I've started using git-p4 to interface\nwith it.  Some of the files included in our depot are cached\npre-compiled binaries which do a great deal of damage to git's\nperformance, so after some research I found that I can \"git update-index\n--assume-unchanged\" on these files.  This is great except that now I'm\nworried that this might prevent git-p4 from doing its thing when someone\nelse updates these files.\n\nSo am I going to miss updates to our cached binaries using this method?\nIs there a better method I should be using in this scenario?\n\nThanks,\nCorey\n"},{"id":"187676","messageId":"20120325135548.GA4664@padd.com","threadId":"29896","inReplyTo":"20120309155848.GA5998@jerec","subject":"Re: How does --assume-unchanged impact git-p4?","fromName":"Pete Wyckoff","fromEmail":"pw@padd.com","sentAt":"2012-03-25T13:55:48Z","receivedAt":"2012-03-25T13:55:48Z","isPatch":false,"sender":{"key":"pw@padd.com","avatar":null},"body":"cmtptr@gmail.com wrote on Fri, 09 Mar 2012 10:58 -0500:\n> My workplace uses Perforce, so I've started using git-p4 to interface\n> with it.  Some of the files included in our depot are cached\n> pre-compiled binaries which do a great deal of damage to git's\n> performance, so after some research I found that I can \"git update-index\n> --assume-unchanged\" on these files.  This is great except that now I'm\n> worried that this might prevent git-p4 from doing its thing when someone\n> else updates these files.\n> \n> So am I going to miss updates to our cached binaries using this method?\n> Is there a better method I should be using in this scenario?\n\nWhen you use \"git-p4 sync\" to pull content from p4, it doesn't\nlook at any of the existing files.  Then when you rebase or\nmerge, changes from p4 will show up in your workspace okay, again\nregardless of the setting of --assume-unchanged.\n\nThe risks outlined in the documentation for git-update-index are\nstill there, but using git-p4 shouldn't add any new ones.\n\n\t\t-- Pete\n"}]}