SVN-在提交主干时提交外部消息 [英] SVN - Committing externals on commit of main trunk

查看:202
本文介绍了SVN-在提交主干时提交外部消息的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

又甜又甜:

我有一个带有外部项目,使我可以通过一个操作将对外部文件的更改与对主干的更改一起提交:

I have one project with an external, which allows me to commit changes to files in that external alongside changes to the main trunk in one operation:

我有另一个带有外部项目,不允许我与主干一起提交更改.

I have another project with an external, which does not allow me to commit changes alongside the main trunk:

最明显的区别是第二个外部文件已签出到复合目录,但除此之外,我无法发现一个区别,那就是阻止SVN一起提交所有内容.

The most obvious difference is that the second external is checked out to a compound directory, but other than that I cannot find a difference that would, to miy mind, be preventing SVN from committing everything together.

这是怎么回事?显然,我希望能够通过一项操作将对外部的更改以及对干线的更改提交给我.在第二种情况下我该如何做到这一点?

What's going on here? Obviously I want to be able to commit changes to externals along with the changes to the trunk in one operation. How can I make this happen in the second case?

推荐答案

答案原来是复合目录.出于某种原因,外部检查直接检入到根项目下的子文件夹(如"SharedLib"),无论实际更改的深度如何,都可以提交更改.无法将外部文件检出到"Externals/SharedLib"之类的文件夹结构中.这也意味着外部对象从各种来源检出到单个子目录中(以避免在只需要一个库的情况下获得整个外部对象)将不允许提交.

The answer turned out to be the compound directory. For some reason, externals checked out to a subfolder immediately under the root project, like "SharedLib", can have changes committed, no matter how much deeper the changes actually are. Externals checked out to a folder structure like "Externals/SharedLib" cannot. That also means that externals checked out from various sources into a single subdirectory (to avoid having to get an entire external when you only need one library) won't allow commits.

我会做的.现在,我知道这是一个问题,当我想与外部人员合作而不只是随身携带它们时,我将调整外部设备的设置方式.

I'll make do. Now that I know it's an issue I'll adjust how externals are set up when I want to actually work with them and not just have them around.

这篇关于SVN-在提交主干时提交外部消息的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆