Can you post up the output from 'git p4 clone', and also see what the output from doing this is:
$ p4 print //depot/some/branch/missingfile.c On 21 April 2015 at 14:33, FusionX86 <fusion...@gmail.com> wrote: > Hi Luke, > > Using -v was a good suggestion. Unfortunately I still don't see what > the problem is. I'm starting to think that maybe I should just create > the client views I need and setup a cron job that p4 syncs and then > git commits/pushes. > > The --preserve-user option is for submitting back to Perforce correct? > I'm hoping to get away with a one-way sync from Perforce to Git...and > then eventually just cut over to Git. > > I also looked at git fusion, but unfortunately the version of Perforce > we're running (2012.1) doesn't meet the requirements for fusion. I > wish it did. > > Good point on developer mindset. I think we definitely have some > training and habit changing in the future. > > Thanks for the suggestions and pointers, it's much appreciated. > > On Mon, Apr 20, 2015 at 1:26 PM, Luke Diamand <l...@diamand.org> wrote: >> On 20/04/15 17:41, FusionX86 wrote: >>> >>> Hello, >>> >>> Hopefully this is an appropriate place to ask questions about git-p4. >>> >>> I started at a company that wants to migrate from Perforce to Git. I'm >>> new to Perforce and have been trying to learn just enough about it to >>> get through this migration. Anyway, I've been playing with git-p4 and >>> have one question/problem to discuss. >>> >>> After setting up the p4 cli client I can 'p4 sync' some >>> //depot/main/app1 which pulls down the files I would expect from the >>> Perforce server. If I use 'git p4 clone //depot/main/app1', I get: >>> >>> "Doing initial import of //depot/main/app1/ from revision #head into >>> refs/remotes/p4/master" >>> >>> But I don't get any files from that depot/folder pulled down. I can >>> git p4 clone other depot/folders though and get some files. I suspect >>> that I'm just not understanding how the git-p4 module works. >> >> >> You could try doing the clone with '-v' to get a bit more information. >> >>> >>> Basically, I'm hoping to setup a live sync of Perforce to Git of >>> certain depots in preparation for the migration. Also, if anyone has >>> pointers or guides for this type of migration, any help is >>> appreciated. >> >> >> I've done something similar in the past. You'll want to enable the >> --preserve-user option, for which you will need admin rights. >> >> If it's a one-way mirror (p4-to-git) then just run git-p4 periodically (if >> you use cron, then try to avoid having two or more instances running at the >> same time). >> >> If you want it to be two-way then it gets a bit more complicated. >> >> You might also want to consider using git fusion, which is Perforce's take >> on this problem. I've not used it myself. >> >> From past experience though I would say the biggest problem is getting >> developers to switch from the P4 mindset (centralized; code review hard to >> do or ignored) to the git mindset (decentralized; code review actively >> supported by the version control system). >> >>> -- >>> To unsubscribe from this list: send the line "unsubscribe git" in >>> the body of a message to majord...@vger.kernel.org >>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>> >> -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
