From: Vitor Antunes <vitor.hda@gmail.com>
To: Arthur <a.foulon@amesys.fr>
Cc: Pete Wyckoff <pw@padd.com>, git@vger.kernel.org
Subject: Re: git-p4 clone @all error
Date: Tue, 6 Nov 2012 00:25:15 +0000 [thread overview]
Message-ID: <20121106002515.5b7eba50@fenix.utopia.dhis.org> (raw)
In-Reply-To: <20121105221212.GA12003@padd.com>
On Mon, 5 Nov 2012 17:12:12 -0500
Pete Wyckoff <pw@padd.com> wrote:
> Thanks, that is interesting output.
>
> Adding Vitor who knows his way around the branch detection
> code. The first mail by Arthur is here, which focuses more
> on the backtrace from "p4 describe" errors, but also suggests
> something is dodgy in branch detection:
>
> http://thread.gmane.org/gmane.comp.version-control.git/208693
>
> I'm not sure if this is a --verbose run, though, as I don't see
> any chatter like "branch is xxx". So I'm not sure if the
> auto-parent detection code got run.
>
> The "unable to resolve reference" comes from refs.c, which is
> when fast-import calls update_branch() on each of the changed
> branches as it is finishing.
>
> Vitor, what could git-p4 have done to create a branch name called
> "refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429"?
> Any other questions for Arthur?
>
Hi Arthur,
Could you please share with us your git-p4.branchList configuration?
Would it also be possible to describe a bit more on your depot
structure? I'm particularly concerned about its integration history.
I suspect the error you are experiencing is connected to a wrong
configuration. Please take into account that each entry must be in the
form of origin:destination, where "origin" is the folder used as the
source of the integration to "destination" when first created.
Vitor
next prev parent reply other threads:[~2012-11-06 0:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 10:44 git-p4 clone @all error Arthur
2012-10-31 13:18 ` Arthur
2012-10-31 14:01 ` Thomas Berg
2012-11-03 23:13 ` Pete Wyckoff
2012-11-05 10:02 ` Arthur
2012-11-05 22:12 ` Pete Wyckoff
2012-11-06 0:25 ` Vitor Antunes [this message]
2012-11-06 8:55 ` Arthur
2012-11-06 13:54 ` Vitor Antunes
2012-11-06 14:20 ` Arthur
2012-11-06 18:35 ` Vitor Antunes
2012-11-06 14:03 ` Arthur
2012-11-03 14:09 ` Pete Wyckoff
2012-11-03 23:07 ` [PATCH] git p4: catch p4 describe errors Pete Wyckoff
2012-11-03 23:12 ` Matt Arsenault
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121106002515.5b7eba50@fenix.utopia.dhis.org \
--to=vitor.hda@gmail.com \
--cc=a.foulon@amesys.fr \
--cc=git@vger.kernel.org \
--cc=pw@padd.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.
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 NNTP newsgroup(s).