SVN是否可以处理区分大小写的问题? [英] Can SVN handle case sensitivity issues?

查看:429
本文介绍了SVN是否可以处理区分大小写的问题?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

是否有一种方法可以强制SVN不区分大小写?我们有一个问题,用户从Linux环境中提交文件说为 file.ext和 File.ext的文件。效果很好。但是,问题是当MAC OSX或Windows上的用户尝试更新/签出时。这两个文件被认为是相同的,并且操作失败。

Is there a way to force SVN to be case insensitive? We have an issue where a user commits from a linux environment with files say "file.ext" and "File.ext". Works just fine. The problem, however, is when a user on a MAC OSX or Windows attempts an update/checkout. The two files are considered the same and the action fails in error.

有没有一种方法可以让SVN首先防止 File.ext和 file.ext的提交?

Is there a way to have SVN prevent the committing of "File.ext" and "file.ext" in the first place?

这个问题相似,但是从Windows角度来看是相同的问题,在这里不是问题。

This question is similar but looks at the same problem from the Windows side, which is not the issue here.

推荐答案

您可以尝试使用预提交的挂钩,例如这一个(不过,我自己也没有尝试过。)

You could try a pre-commit hook, such as this one (didn't try it myself, however).

我认为吸引用户注意它已经排除?我一直在Linux上工作,但通常认为文件名不区分大小写。 e。与 me 一样,无论操作系统如何,它们都是相同的。

I assume that getting your users watch out for it has already been ruled out? I work on Linux all the time, but typically consider filenames case-insensitive, i. e. to me, they are the same, no matter what the OS thinks.

这篇关于SVN是否可以处理区分大小写的问题?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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