Re: git to p4 conversion

> I... wonder if we're maybe talking past one another here...
>
> Let's take a few things from the top, just in case... If we think
> about the perforce setup (before we start doing any git stuff)... You
> have a perforce workspace/client-spec, right? That is - a setup that
> tells perforce where you want the files to be placed on your hard
> drive when you do a standard "p4 sync". Let's call it ~/p4root/ and
> let us say that your project will then be synced by perforce to
> ~/p4root/myproj/
>
> When you want to do a git-p4 clone, you should definitely be *outside*
> of ~/p4root/ . Let's say we have a ~/gitroot/ as well. So do cd
> ~/gitroot/ so that the git-p4 clone will be under ~/gitroot/myproj/ ;
> and then do all the git-p4 stuff (clone, add remote, fetch, rebase,
> sync, submit).
>
> I think Vitors point was that before you do git-p4 submit, you should
> clean - not ~/gitroot/myproj - but ~/p4root/myproj/.
>
> This is probably not something that you need to do everytime you want
> to submit back to perforce, but since we have had some rounds with
> trial-and-error with this, we have probably placed some dirty files
> inside the perforce folders... Make sure that you don't have files
> opened in perforce before you sync.
>
> Clearer? More confused? Best of luck anyway :)
>
>    -- Tor Arvid
>