从 perforce 发布到 svn？
我有两个使用 Perforce 进行内部管理的项目。这些也使用 svn 发布到 google 代码。
我目前有一组脚本从我的主目录中的 perforce 区域复制到 svn 区域，同步它，比较它，然后提交它。
看来我可以在 perforce 管理的区域中进行 svn checkout 并就地执行 svn 操作。
有人做过类似的事情吗？有任何提示、指示等吗？
I have two projects which I manage internally using Perforce. These are also published to google code using svn.
I currently have a set of scripts that copy from the perforce area in my home directory to the svn area, sync it, diff it, and commit it.
It seems that I might be able to just do a svn checkout in the perforce-managed area and perform the svn operations in place.
Has anybody done something like that? Any hints, pointers, etc.?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我不明白为什么不，如果你可以强制忽略 .svn 目录，那么 SVN WC 只是一个普通的文件目录。
您可以对这些文件进行更改，并使用 SVN 正常提交它们 - SVN 仅使用 .svn 目录来检测是否有任何更改并生成发送到存储库的差异。 Perforce 不会影响其中的任何部分 - 只要你可以让它忽略 .svn 目录。
I don't see why not, if you can make perforce ignore the .svn directories, then a SVN WC is just an ordinary directory of files.
You can make your changes to those files, and commit them as normal using SVN - SVN simply uses the .svn dirs to detect whether anything has changed and to generate the diffs to send to the repository. Perforce won't affect any part of that - as long as you can make it ignore the .svn dirs.