git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Matthieu Brucher <matthieu.brucher@gmail.com>
To: Vitor Antunes <vitor.hda@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: Mon, 8 Jul 2013 15:03:32 +0100	[thread overview]
Message-ID: <CAHCaCkJDWTKQk4SrspXVCsCoHStRTaR_PSEgkvqwWHdmiLuY2w@mail.gmail.com> (raw)
In-Reply-To: <CAOpHH-WxOhfYYOY8z5rc+O1B5QD8g22L9DFrNFEAtp9YwH+V_A@mail.gmail.com>

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.

Thanks,

Matthieu



2013/7/8 Vitor Antunes <vitor.hda@gmail.com>:
> On Mon, Jul 8, 2013 at 12:10 PM, Matthieu Brucher
> <matthieu.brucher@gmail.com> wrote:
>> Without the spec client, it seems that the branches are recognized,
>> but there are some many binary files that I need to remove them during
>> the migration.
>> I tried setting a .gitignore beforehand, but it is not respected (I
>> tried to remove some folders with folder/ in .gitignore, but the
>> folder are still imported).
>> It there a switch for the import somewhere?
>
> Hi Matthieu,
>
> Unfortunately I've never tested the branch detection together with spec
> configuration. But there is a test case for it in the code that refers
> to the following question in StackOverflow:
>
> http://stackoverflow.com/questions/11893688
>
> Could you also tell us which version of git you are using?
>
> Pete, maybe you can help Matthieu further on this question?
>
> Thanks,
> Vitor



-- 
Information System Engineer, Ph.D.
Blog: http://matt.eifelle.com
LinkedIn: http://www.linkedin.com/in/matthieubrucher
Music band: http://liliejay.com/

  reply	other threads:[~2013-07-08 14:03 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 [this message]
2013-07-13  0:28                       ` Vitor Antunes

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=CAHCaCkJDWTKQk4SrspXVCsCoHStRTaR_PSEgkvqwWHdmiLuY2w@mail.gmail.com \
    --to=matthieu.brucher@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=pw@padd.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.
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).