Sean, Fri, Jun 02, 2006 15:43:57 +0200: > "Alex Riesen" <raa.lkml@xxxxxxxxx> wrote: > > > BTW, can I suggest to import the _currently_ synced state? > > > > Note that it never syncs specifically to head, it explicitly asks for > each revision along the branch and tt doesn't know anything about your > working state, it can only import commits. So did get that part right (I didn't actually tried your script, just read the code). > Are you looking for the ability to create a single git branch which has Well, I'm not quite sure it's at all possible... Perforce has a strange ways for doing history: it is kept for each file (as in CVS), but you can bundle changes in many files into one "change". Perforce also has no branches (in the GIT's meaning of the term). These by Perforce are just server-side directories, without any relevance to the source whatsoever (just copies). > the history of the combined view of your stitched together client mappings > rather than the independent branches held by the server? I'm rather looking for a ability to manage a single branch where import "sync" events appear as a merge of changes to the files involved in the sync. I just haven't figured out yet how to "break" a Perforce change into changes to single files and import that broken up commit into git as a merge. I hope that was clear enough... I think understanding how cvs/svn imports work should help here - Perforce is actually nothing very different from them. - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html