From: Vitor Antunes <vitor.hda@gmail.com>
To: git@vger.kernel.org
Subject: Re: git p4 clone not processing branches properly
Date: Fri, 5 Jul 2013 17:56:59 +0000 (UTC) [thread overview]
Message-ID: <loom.20130705T195116-413@post.gmane.org> (raw)
In-Reply-To: CAHCaCk+8EehnwMP98EX=cdoyQof=zPj65Vyd_YaADVquztOYww@mail.gmail.com
Matthieu Brucher <matthieu.brucher <at> gmail.com> writes:
>
> Hi,
>
> I'm trying to convert a Perforce repository to git, knowing that:
> - I use client specs to remove a bunch of folders containing binaires
> (several GiB)
> - branch mappings may not be properly set, and I can't change them
>
> Now, the branches are layout like this:
> - Branch/Main <- master
> - Branch/Feature1
> - ...
> - Releases/2013
> - ...
> I would like to have these branches and releases branches inside by
> cloned git repository, but this doesn't work. I keep on getting each
> file with Project/Branch/Main as well as Project/Branch/Feature1 and
> all others in my master branch.
> I tried to add branchLists like this:
> branchList = Branch/Main:Releases/2013
> branchList = Releases/2013:Branch/Feature1
> but it doesn't change a thing with the following command:
> git p4 clone --verbose --use-client-spec --detect-branches
> //Depot/Project <at> specificrevision
>
> I can see that branches are detected from the Perforce server, but
> none are actually detected for this specific project:
> p4-git branches: []
> initial parents: {}
>
> Can someone give a pointer to a tutorial or something for a complex
> case like this?
Hi Matthieu,
Could you please try using //Depot/Project<at>all instead of selecting a
specific revision?
Also, by using that command it means that the following depot paths must
exist:
//Depot/Project/Branch/Main
//Depot/Project/Releases/2013
//Depot/Project/Branch/Feature1
I've never used the --use-client-spec, so I'm not sure if that will not
break the branch detection code.
Cheers,
Vitor
P.S. - Please keep me in CC because I'm not subscribed to the mailing
list.
next prev parent reply other threads:[~2013-07-05 17:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHCaCkJ+zRwu67QsYidmvcwtWtPPd4XPBYDaTnHLt9HrTSDM3A@mail.gmail.com>
2013-07-05 13:16 ` git p4 clone not processing branches properly Matthieu Brucher
2013-07-05 17:56 ` Vitor Antunes [this message]
2013-07-05 18:11 ` Matthieu Brucher
2013-07-05 18:36 ` Vitor Antunes
2013-07-05 18:45 ` Matthieu Brucher
2013-07-08 10:09 ` Matthieu Brucher
2013-07-08 10:24 ` Vitor Antunes
2013-07-08 10:51 ` Matthieu Brucher
2013-07-08 11:10 ` Matthieu Brucher
2013-07-08 13:43 ` Vitor Antunes
2013-07-08 14:03 ` Matthieu Brucher
2013-07-13 0:28 ` Vitor Antunes
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
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 \
--in-reply-to=loom.20130705T195116-413@post.gmane.org \
--to=vitor.hda@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).