All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitor Antunes <vitor.hda@gmail.com>
To: Grant Limberg <glimberg@gmail.com>
Cc: Pete Wyckoff <pw@padd.com>, git@vger.kernel.org
Subject: Re: [git-p4] Trouble importing all perforce branches into git repository
Date: Mon, 23 May 2011 11:54:18 +0100	[thread overview]
Message-ID: <BANLkTi=TCyyS7Q=3BnLcG=yhL_boH=w1XA@mail.gmail.com> (raw)
In-Reply-To: <398FA881-E4A1-49AC-80F2-2D46E9F2ABB9@gmail.com>

Hi Grant,

I think I saw that happening when there is nothing to import or in
situations where the parent of a certain branch does not exist.

Perforce does not strictly require branch definitions to allow a branch
structure/flow. It is quite possible that you are integrating stuff
around without using "branch specs". When git-p4 is importing your P4
database it will look at all branches available in the server, including
ones from other depots. So it is possible that while you are seeing a
big list of branches being processed, none apply to the branch structure
you are trying to import.

Could you please confirm that you have Perforce branch specs for all
branches that you are trying to import?

Thanks,
Vitor

  reply	other threads:[~2011-05-23 10:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-19 19:31 [git-p4] Trouble importing all perforce branches into git repository Grant Limberg
2011-05-22 11:49 ` Pete Wyckoff
2011-05-23  3:27   ` Grant Limberg
2011-05-23 10:54     ` Vitor Antunes [this message]
2011-05-23 16:18       ` Grant Limberg
2011-05-23 17:38         ` Vitor Antunes
2011-05-23 20:06           ` Grant Limberg
2011-06-16  8:28             ` tumik
2011-06-16  8:51               ` Thomas Berg
2011-06-16  9:35                 ` tumik
2011-06-16 10:05                   ` Thomas Berg

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='BANLkTi=TCyyS7Q=3BnLcG=yhL_boH=w1XA@mail.gmail.com' \
    --to=vitor.hda@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=glimberg@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.