将修订与颠覆性相结合的困难
早上好，
假设开发人员在两个不同分支的两个不同项目中提交了独特的修订版（假设为 4582）。例如： 项目A（分支/ProjectA/V2.0） 项目 B (branches/ProjectB/V2.1)
我们想要做的是将这个版本 4582 一步合并到其他两个分支（即不需要单独执行合并），例如： 项目A（分支/ProjectA/V2.0）===>项目A（分支/ProjectA/V1.4） 和 项目B（分支/ProjectB/V2.1）===>项目 B (branches/ProjectB/V1.3)
有人知道是否可以使用 subersive 只需一步即可完成此场景？
谢了， 丹尼尔.
Good morning,
Supose a developer has commited a unique revision (let's say 4582) in two different projects which are in two different branches. For example:
Project A (branches/ProjectA/V2.0)
Project B (branches/ProjectB/V2.1)
What we would like to do is merging this revision 4582 to other two branches in a single step (i.e. without the necessite to perform the merge separetedly), for example:
Project A (branches/ProjectA/V2.0) ===> Project A (branches/ProjectA/V1.4)
AND
Project B (branches/ProjectB/V2.1) ===> Project B (branches/ProjectB/V1.3)
Anybody knows if is it possible to do this scenario in just one step using subersive?
tks,
Daniel.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我不认为颠覆能够做到这一点。
即使使用控制台客户端，当直接在存储库上工作时，您也必须将合并分为两个步骤。
如果它在一次提交中如此重要，您可以签出整个存储库，执行两个合并步骤，然后提交整个存储库。但这将需要大量磁盘空间，因为所有标签、分支等都会被检出。
I don't think subversive is able to do this.
Even using the console client you would have to split the merge in two steps, when working directly on the repository.
If it is that important that it is in one commit, you could checkout the whole repository, do both merge steps and then commit the whole repository. But that will need much disk space, because all tags, branches, etc. are checked out.