I've got a git repository that I'd like to mirror to a Perforce repository. I've downloaded the git-p4 script (the more recent version that doesn't give deprecation warnings), and have been working with that. I've figured out how to pull changes from Perforce, but I'm getting an error when I try to sync changes from the git repo back. He...
At work, development uses perforce to handle code sharing. I won't say "revision control", because we aren't allowed to check in changes until they are ready for regression testing. In order to get my personal change sets under revision control, I've been given the go-ahead to build my own git and initialize the client view of the perf...
I'm trying to use git-p4 to clone perforce depot. I keep running into a problem in the git-p4 script, where git-p4 tries to access a dict key that is not defined and throws a trace. [~/p4/prod@ernie02] (master) $ git p4 sync --verbose --use-client-spec //depot/prod/ Reading pipe: git config git-p4.user Reading pipe: git config git-p4....
My p4 repository has a structure similar to: //depot/project/branch1 //depot/project/branch2 //depot/project/branch3 ... etc However, when I use git-p4 to clone "project", all 3 branches are not considered as branches and all get cloned into the single master branch. This is how I'm invoking git-p4: git-p4 clone --detect-branches ...
At work, we use Perforce for version control. There are problems with this: 1) with this centralized model, we can't check in changes until they are ready for regression. This means that we have no revision control during the development process. 2) We don't back up our client view of the depot, so our work is unsafe until we can chec...
I'm trying to mirror a perforce repository, and git-p4 performs well enough on the main branch. I simply have to call git-p4 rebase. I'm also trying to mirror a different branch, but that's not working out so easily. I thought I could just do a git-p4 rebase --branch=p4/whatever //open/branches/whatever but rebase appears to ignore those...
I have the task of migrating my team & source from git to Perforce, and I'm looking for ideas on how to move the git history into p4. I would be happy moving master branch only. However, even that is proving problematic. I'm using the wonderful git-p4 tool. I create an destination area in my p4 workspace, and use git p4 clone //depot/S...
I imported a large repo using git-p4, and discovered that I have some strangely mixed-case filenames, e.g.: dirA/DIRb/file1.txt and then other files like so: DIRa/dirB/FILE2.txt and so on. These get entered into the repo this way because git-p4 uses fast-import. This causes Git to mysteriously claim that there are untracked directo...
I'm runnining on Windows, with the windows p4 client, and git installed via Cygwin. The p4 client advertises how its syntax is regular across platforms and all that, so that should be hunky-dory. So when I go to git-p4 clone --verbose //depot/path/to/source, it lists out all the files in the repository as though they were being checked ...