Re: git-p4: cloning with a change number does not import all files
- Date: Sat, 2 Dec 2017 17:55:28 +0000
- From: Luke Diamand <luke@xxxxxxxxxxx>
- Subject: Re: git-p4: cloning with a change number does not import all files
On 2 December 2017 at 15:35, Patrick Rouleau <prouleau72@xxxxxxxxx> wrote:
> On Fri, Dec 1, 2017 at 7:45 AM, Lars Schneider <larsxschneider@xxxxxxxxx> wrote:
>> Oh, I am with you. However, I only used git-p4 for a very short time in the
>> way you want to use it. Therefore, I don't have much experience in that kind
>> of usage pattern. I was able to convice my management to move all source to
>> Git and I used git-p4 to migrate the repositories ;-)
>> Here is a talk on the topic if you want to learn more:
> Sadly, there is no way I convince the company to switch to git. They
> have acquired
> many companies in the past years and they have standardized around Perforce.
> It is in part because they want access control and they need to store
> a lot of binary
> files (including big VM images).
> I keep this video close to explain why I like git:
I feel your pain.
I think I've sort of stumbled across something like the problem you've
described in the past. Perhaps the files you need have been deleted
and then re-integrated or some such.
Would you be able to take a look at some files with this problem and
see if you can spot what's happened to it ("p4 changes" and perhaps
"p4 changes -i").
One thing that can certainly happen is that Perforce gets *very*
confused if you start getting too clever with symlinked directories,
and git-p4 can only do so much in the face of this. But it may be