On Monday 11 June 2007 22:51:40 Kevin Green wrote: [...] > Anyway, grabbed git-p4 and tried it three ways: > > 1) git-p4 clone //depot/path/repo@all > > I don't like this because it creates a git repository under "repo" > subdir. To make a long store short, we have a very strict namespace for > development... The path ends in src and I'd like the .git repository to > be under src. Fair enough :) > So, I tried this one level up: > > 2) git-p4 clone //depot/path/repo@all src > > But that dies with a mkdir error because 'src' already exists. I want to > submit a patch, but wanted to check with you first to see if that's the > desired behaviour (I don't think it should fail though) because maybe you > want to stop someone from scribbling on an already present git repository? > > I would want to just go for a "if it doesn't exist yet, create it, > otherwise, forge ahead" behaviour. I attach the patch after my .sig... Thanks for the patch. Applied and pushed out. > 3) Tried without clone: > > $ git init > $ git-p4 sync //depot/path/repo@all > > This looks like it's pulling down all the revisions, but it doesn't > actually put any code in there. I'm left with the same situation as > git-p4import.py. > > Actually, not even. I don't even have the commit history... Actually... the import worked just fine, but I admit that it is not obvious _where_ the import went. I've just pushed out a change that makes git-p4 sync in this case also print out the ref. By default git-p4 sync imports into refs/remotes/p4/master, so after the above command a simple git branch -r should print p4/HEAD p4/master so you could for example just create a new master branch based on your p4 import using git branch master p4 git checkout master I hope this helps :) Simon
Attachment:
signature.asc
Description: This is a digitally signed message part.
