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

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

From
PWPete Wyckoff <pw@padd.com>
Date
Mar 25, 2012, 13:55 UTC
Message-ID
<20120325135548.GA4664@padd.com>
In-Reply-To
<20120309155848.GA5998@jerec>
cmtptr@gmail.com wrote on Fri, 09 Mar 2012 10:58 -0500:
Show 10 quoted lines
> 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?

When you use "git-p4 sync" to pull content from p4, it doesn't look at any of the existing files. Then when you rebase or merge, changes from p4 will show up in your workspace okay, again regardless of the setting of --assume-unchanged.

The risks outlined in the documentation for git-update-index are still there, but using git-p4 shouldn't add any new ones.

		-- Pete
Previous: Corey Thompson
Message 2 of 2 in “How does --assume-unchanged impact git-p4?”
  1. Corey ThompsonMar 9, 2012
  2. Pete WyckoffMar 25, 2012

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.