From: Pete Wyckoff <pw@padd.com>
To: Corey Thompson <cmtptr@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: How does --assume-unchanged impact git-p4?
Date: Sun, 25 Mar 2012 09:55:48 -0400 [thread overview]
Message-ID: <20120325135548.GA4664@padd.com> (raw)
In-Reply-To: <20120309155848.GA5998@jerec>
cmtptr@gmail.com wrote on Fri, 09 Mar 2012 10:58 -0500:
> 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
prev parent reply other threads:[~2012-03-25 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 15:58 How does --assume-unchanged impact git-p4? Corey Thompson
2012-03-25 13:55 ` Pete Wyckoff [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120325135548.GA4664@padd.com \
--to=pw@padd.com \
--cc=cmtptr@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).