Re: git to p4 conversion
- From
Endre Czirbesz <endre@czirbesz.hu>
- Date
- Feb 4, 2011, 16:08 UTC
- Message-ID
- <AANLkTi=dZdSqcNckyU7Lb2Zj-khfj=Xiyzbv7LSC+zT2@mail.gmail.com>
- In-Reply-To
- <AANLkTi=_spLE-KMnou-2LLQjwq4FUZxNr9pk7D9C=4PK@mail.gmail.com>
2011/2/4 Tor Arvid Lund <torarvid@gmail.com>:
> Well, I can get it to work if I do: > $ git p4 sync > > before the 'git p4 submit'.
Same result. :(
My current workflow is:
$ rm -rf projdir $ git-p4 clone //depot/projdir/...@all $ cd projdir $ git remote add gitremote endre@gitserver/gitrepo.git $ git fetch -q gitremote $ git checkout -b tempbranch gitremote/master $ git rebase -q master $ git-p4 sync $ git-p4 submit
The result is still tons of file already exists in working directory messages.
> Try that, and see if it works for you. (BTW, when committing > half-works, and then fails, oftentimes you need to do a bit of cleanup > in perforce... Revert files, manually remove files created by git > inside your p4 clientspec root directory, that sort of thing...)
I dropped the whole directory, and then recreated it, I do not know any better 'cleanup'. :)
Rgds,
Endre