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@xxxxxxxxx>: > On Mon, Jul 8, 2013 at 12:10 PM, Matthieu Brucher > <matthieu.brucher@xxxxxxxxx> 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/ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html