From: Vitor Antunes <vitor.hda@gmail.com>
To: Matthieu Brucher <matthieu.brucher@gmail.com>
Cc: Pete Wyckoff <pw@padd.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: git p4 clone not processing branches properly
Date: Sat, 13 Jul 2013 01:28:16 +0100 [thread overview]
Message-ID: <CAOpHH-UBRJ08KEnUdGMy6F3eqUkUWSsnuDCCciUOHsg+4TpM2w@mail.gmail.com> (raw)
In-Reply-To: <CAHCaCkJDWTKQk4SrspXVCsCoHStRTaR_PSEgkvqwWHdmiLuY2w@mail.gmail.com>
On Mon, Jul 8, 2013 at 3:03 PM, Matthieu Brucher
<matthieu.brucher@gmail.com> wrote:
> Hi,
>
> I tried without spec, but then it tried importing everything, even
> though there was a .gitignore and a .git/config/exclude file.
> Then, it crashed during the importation because it could find an old
> branch (I don't have access to everything on the repository), so I
> tried importing just the recent past, but then it failed because it
> identified a branch names Branch/Main/src...
> It is starting to feel as if I will have to compromise between
> something that works but without branches and without the proper names
> (the files are named Project/Branch/Main/...) or having the proper
> names, but with all binaries, bogus branches...
> I know it is not due to git, it is mainly that Perforce and git have
> very different workflows. Or perhaps with any luck, the server is up
> to date, and I can find a way of using Perforce's bridge.
Hi Matthieu,
I created a simple test case where I added a file to one of the branches in
P4 but excluded it in the client spec. During synchronization git p4
correctly ignored it.
Please check which git version you are using. It is possible the issue you
are experiencing was fixed in a more recent version.
Also, if possible, please try creating a simple test case that replicates
your issue (p4 and p4d are free to use when the repo is only used by one
person). If you record the commands you used and share them with me I will
be able to better check this issue on my side.
Cheers,
Vitor
prev parent reply other threads:[~2013-07-13 0:28 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
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 [this message]
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=CAOpHH-UBRJ08KEnUdGMy6F3eqUkUWSsnuDCCciUOHsg+4TpM2w@mail.gmail.com \
--to=vitor.hda@gmail.com \
--cc=git@vger.kernel.org \
--cc=matthieu.brucher@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.
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).