On 5/8/07, Simon Hausmann <simon@xxxxxx> wrote:
> > It also doesn't require any additional meta-data. Instead every import > > commit has a line added to the log message that contains the Perforce > > path the changeset comes from as well as the change number. git-p4 > > sync/rebase "parses" this on the last commit in the "p4" git branch to > > find out where to continue importing for incremental imports. > > How do you handle that patchwork of mappings synced to diverse revisions > that P4 clients tend to become? Don't you have to save change number or > revision for _each_ file? I'm not sure I understand the question. I don't really use the p4 client view at all. ...
Ah, you're _that_ lucky...
> > problems with fast-import when trying that. Also the support for Perforce > > branches isn't quite working yet. > > AFACS, it is impossible: Perforce does not have branches (in Git's meaning > of the word). It only has directories. Integration (it is something like > "in-repo-copy") metadata are just duct-taped on it (that stupid > branchspec). True, it probably depends a bit on the depot organization. For example we have //depot/qt/main and then branches like //depot/qt/4.3 or research branches like //depot/qt/research/somecoolfeature . That's the kind of structure I'd like to map to git, ...
Recreating it anywhere, not just in Git, would be stupid. As it is in Perforce.
> > Also I've never tried it on Windows and I expect problems as the script > > uses pipes, calls "patch", etc. > > ...and case-sensitivity. BTW, how does your script handle filenames with > special characters and spaces in them? I don't really treat them special. I get the file name from the output of "p4 describe" (using the Guido option :) and pass it on to git-fast-import.
You seem to assume that the names never contain double quotes and backslashes. For example in the names of directories. - 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
