From: Luke Diamand <email@example.com>
To: Patrick Rouleau <firstname.lastname@example.org>
Cc: Lars Schneider <email@example.com>,
Git Users <firstname.lastname@example.org>
Subject: Re: git-p4: cloning with a change number does not import all files
Date: Sat, 2 Dec 2017 17:55:28 +0000 [thread overview]
Message-ID: <CAE5ih78GOFqe_Vb3k_-jPiS7zbX1EdvYmsUyWvKKy=xOH9WrcQ@mail.gmail.com> (raw)
On 2 December 2017 at 15:35, Patrick Rouleau <email@example.com> wrote:
> On Fri, Dec 1, 2017 at 7:45 AM, Lars Schneider <firstname.lastname@example.org> 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
next prev parent reply other threads:[~2017-12-02 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-25 20:35 git-p4: cloning with a change number does not import all files Patrick Rouleau
2017-11-27 12:52 ` Lars Schneider
2017-11-29 3:48 ` Patrick Rouleau
2017-12-01 12:45 ` Lars Schneider
2017-12-02 15:35 ` Patrick Rouleau
2017-12-02 17:55 ` Luke Diamand [this message]
2017-12-02 19:58 ` Patrick Rouleau
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).