From: Pete Wyckoff <pw@padd.com>
To: Grant Limberg <glimberg@gmail.com>
Cc: Vitor Antunes <vitor.hda@gmail.com>, git@vger.kernel.org
Subject: Re: [git-p4] Trouble importing all perforce branches into git repository
Date: Sun, 22 May 2011 07:49:17 -0400 [thread overview]
Message-ID: <20110522114917.GA19927@arf.padd.com> (raw)
In-Reply-To: <5A927B4F-7242-48AD-BC1C-BCA490A251C4@gmail.com>
glimberg@gmail.com wrote on Thu, 19 May 2011 19:32 +0000:
> [git-p4 automatic branch detection]
> > git p4 clone --verbose --detect-branches --max-changes=100 //project/...@all
I worry that --max-changes prevents it from pulling in the
ref for Branch-foo, and this confuses the automatic branch
detection that assumes it has all its parents.
It would certainly be more reliable if you did "git-p4 sync
--branch foo //project/foo@all" for each branch you care about.
Vitor has some modifications to auto-branch detection that might
be useful, or maybe some thoughts as to what's going on.
-- Pete
(Vitor: full mail is here:
http://article.gmane.org/gmane.comp.version-control.git/173996/ )
next prev parent reply other threads:[~2011-05-22 11:49 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 [this message]
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
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=20110522114917.GA19927@arf.padd.com \
--to=pw@padd.com \
--cc=git@vger.kernel.org \
--cc=glimberg@gmail.com \
--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.
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).