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 18:38:03 +0100 [thread overview]
Message-ID: <BANLkTik+Zp1Fvi_zABCtAZH0RKA68n5Svw@mail.gmail.com> (raw)
In-Reply-To: <34E33A18-B9C4-4CA9-B96C-79B0E2BDCD44@gmail.com>
Hi Grant,
> The "Branch-foo" that git-p4 is crashing on does have a branchspec in
> Perforce. I cannot, however guarantee that branchspecs were
> correctly created and used for all integrates in the repository. It
> was created long before I started working here.
You can create the branch specs now. There is no requirement for them to
have been created at the time of the integration.
I've sent a patch to this mailing list [1] that adds the possibility of
creating these branches in a gitconfig file. If you feel brave enough,
please give it a try. The patch is missing a test case, which I still
did not have time to review and send
> Is there a way to limit --detect-branches to only certain branches
> that I can ensure do have branchspecs?
If you have an incremental structure you could limit the cloning to a
subset of the directories. I am not aware of any other way. Maybe
someone else in the mailing list can shed some light...? :)
Vitor
[1] http://thread.gmane.org/gmane.comp.version-control.git/167998/focus=168000
next prev parent reply other threads:[~2011-05-23 17:38 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
2011-05-23 16:18 ` Grant Limberg
2011-05-23 17:38 ` Vitor Antunes [this message]
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=BANLkTik+Zp1Fvi_zABCtAZH0RKA68n5Svw@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 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).