From: Matthieu Brucher <matthieu.brucher@gmail.com>
To: Vitor Antunes <vitor.hda@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git p4 clone not processing branches properly
Date: Mon, 8 Jul 2013 11:09:03 +0100 [thread overview]
Message-ID: <CAHCaCkL=ghxktJHDEVPfn73o-6oPQnXQv1NBCwxkwsM==-bQ4A@mail.gmail.com> (raw)
In-Reply-To: <CAHCaCkJDNqhd0UqnZhrA13V=J_yJBr17BuWohjMRADCPYFiQ4Q@mail.gmail.com>
Hi again,
I tried with @all, but it didn'y work as expected. It imported a bunch
of revisions (but no files?) and ended with:
Reading pipe: ['git', 'config', '--bool', 'git-p4.importLabels']
Not checking out any branch, use "git checkout -q -b master <branch>"
executing git config --bool git-p4.useclientspec true
And when I tried to checkout Branch/Main, it failed with
fatal: Cannot update paths and switch to branch 'master' at the same time.
Did you intend to checkout 'Branch/Main' which can not be resolved as commit?
Thanks,
Matthieu
2013/7/5 Matthieu Brucher <matthieu.brucher@gmail.com>:
>>> I can try. Indeed, at this revision, the two other branches do not yet
>>> exist. But @all will get everything? Last time, I only got head
>>> (IIRC).
>>
>> Our P4 server has a limitation on the number of lines returned by "p4
>> changes" command, so sometimes I have to use @change_start,@change_stop
>> instead of @all. You might want to use this range limitation to test
>> git-p4 by limiting to a small number of changelists that allows you to
>> check if at least one branch is correctly detected.
>
> I didn't know about this. I wanted to start the cloning at some point
> in the past, that's why I used the @123456789 notation.
>
>>>> 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
>>>
>>> Yes, they indeed do.
>>
>> In this case the problem should not be in branchList configuration.
>>
>>>> I've never used the --use-client-spec, so I'm not sure if that will not
>>>> break the branch detection code.
>>>
>>> I need to do that because if I don't, the depot is clobbed with
>>> binaries. Or perhaps if I put some .gitignore stuff, I might not do
>>> this?
>>
>> Keep using it, at least for now. If everything else fails we can look at
>> this again.
>
> OK, I'll send a mail on Monday (forgot it was the week end tomorrow...)
>
> Cheers,
>
> Matthieu
> --
> Information System Engineer, Ph.D.
> Blog: http://matt.eifelle.com
> LinkedIn: http://www.linkedin.com/in/matthieubrucher
> Music band: http://liliejay.com/
--
Information System Engineer, Ph.D.
Blog: http://matt.eifelle.com
LinkedIn: http://www.linkedin.com/in/matthieubrucher
Music band: http://liliejay.com/
next prev parent reply other threads:[~2013-07-08 10:09 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
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 [this message]
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='CAHCaCkL=ghxktJHDEVPfn73o-6oPQnXQv1NBCwxkwsM==-bQ4A@mail.gmail.com' \
--to=matthieu.brucher@gmail.com \
--cc=git@vger.kernel.org \
--cc=vitor.hda@gmail.com \
/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).