On 19/09/2007, Sam Vilain <sam@xxxxxxxxxx> wrote: > Reece Dunn wrote: > > There is no need to create yet another Perforce importing tool, git-p4 > > works well in most cases. If we focus on improving git-p4, extending > > it to support the functionality mentioned here, fix the issues that > > there are with it, then that will be more beneficial to the community > > as they will not have to learn another tool with a different set of > > bugs and issues. > > I like my approach; it's clean and I think shows a tasteful level of > distrust towards the sanity and integrity of the data held by Perforce. > Actually it really helped me understand what was really going on; > because the information as displayed by for instance "p4 integrate" is > a lot more confusing than the underlying tables (IMHO). I agree. What I wasn't clear about in that paragraph, but had eluded to in other comments in that email, is that having both git-p4 and git-p4raw is a good thing as they operate on two differing use cases. What I was referring to there is to have another equivalent of git-p4 that interfaced using the p4 client. - Reece - 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
