From: Patrick Rouleau <firstname.lastname@example.org>
To: Luke Diamand <email@example.com>
Cc: Lars Schneider <firstname.lastname@example.org>,
Git Users <email@example.com>
Subject: Re: git-p4: cloning with a change number does not import all files
Date: Sat, 2 Dec 2017 14:58:44 -0500 [thread overview]
Message-ID: <CAL1_K8DGVzcbWFPz3vbEntB08sEhrV-j-sLxAh0QhV=8KRGf-Q@mail.gmail.com> (raw)
On Sat, Dec 2, 2017 at 12:55 PM, Luke Diamand <firstname.lastname@example.org> wrote:
> 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").
Sorry, but these commands only show the date and an extract of the commit
> 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
> something else.
Overall, the depot history is very "messy". It contains a lot of projects. The
project on which I work has reach v5 and it has been branched from v4.
From p4v's "show graph", I can see there was a 'main' branch at some point,
but it doesn't exist anymore.
One of the files missing from my clone only has 2 revisions and it was created
in the v5 branch. It was created at 608436 and modified at 608816. I cloned
from 610443, mainly because we added a feature branch and I want to access
it from git too (610443 is one month before the branch creation).
I will play a little bit with p4 to see if I can locate where the problem comes
from and maybe hack git-p4 to make it more verbose.
prev parent reply other threads:[~2017-12-02 20:00 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
2017-12-02 19:58 ` Patrick Rouleau [this message]
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).