On Fri, 8 May 2009, Carl Mercier wrote: > Thank you. > > What I'm trying to accomplish is a little bit different. We've been using Git > with a remote server for so long, we don't want to give that up. (and we also > can't for some reasons). So what I was hoping to do was simply keep working > with out remote Git server as normal, and then have another server pull from > Git and submit to P4. > > We have many Git repos we'd like to store into P4 subdirectories. For > example: > > website.git -> //SecTech/website > api.git -> //SecTech/api > > I just can't seem to get this to work because git-p4 seems to expect a brand > new Git repo to work properly. You're going to have a whole bunch of problems, most likely, including that Perforce doesn't suppose the history structure that git uses (where a revision can have multiple parents without these revisions having different codelines). Most likely, what you actually want to do is essentially send Perforce git's reflog. You should be able to write a short post-update hook that takes the diff between the before and after, add/edit/delete the files that changed, change a client workspace, and submit it. -Daniel *This .sig left intentionally blank* -- To unsubscribe from this list: 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