I am seeting up Apache server with TortoiseSVN for local source code repository. Currently on trial purpose I am setting only two users. Is it possible for administrator to set up some thing so that file get compulsory locked once its checkout (copy to working directory) by some one.
我正在使用TortoiseSVN将Apache服务器用于本地源代码存储库。目前正在试用,我只设置了两个用户。是否有可能管理员设置一些东西,以便文件一旦被检出(复制到工作目录)就被强制锁定。
Abhijit Dhopate
2 个解决方案
#1
2
The main reason you might want to do this on subversion is for binary files (i.e. images, etc.) that are difficult or impossible to 'merge'. In those cases, each user can request a lock on a file. There is also a svn property (needs-lock) that can be applied to files that makes them read-only on checkout, and read-write when you lock, so that you remember to request the lock before editing.
您可能希望在subversion上执行此操作的主要原因是难以或无法“合并”的二进制文件(即图像等)。在这些情况下,每个用户都可以请求锁定文件。还有一个svn属性(needs-lock)可以应用于文件,这些文件在结帐时使它们只读,并在锁定时进行读写,这样您就可以记得在编辑之前请求锁定。
See the chapter on locking in the svn book.
请参阅有关锁定svn书籍的章节。
#2
0
Wouldn't that defeat one of the purposes of a concurrent versioning system like SubVersion? Generally, you'll check out a block of files, but the server doesn't know whether anyone is editing those files. Why not allow another user access to those files and deal with the results if a conflict emerges?
难道这不会破坏像SubVersion这样的并发版本系统的目的之一吗?通常,您将检出一个文件块,但服务器不知道是否有人正在编辑这些文件。为什么不允许其他用户访问这些文件并在出现冲突时处理结果?
#1
2
The main reason you might want to do this on subversion is for binary files (i.e. images, etc.) that are difficult or impossible to 'merge'. In those cases, each user can request a lock on a file. There is also a svn property (needs-lock) that can be applied to files that makes them read-only on checkout, and read-write when you lock, so that you remember to request the lock before editing.
您可能希望在subversion上执行此操作的主要原因是难以或无法“合并”的二进制文件(即图像等)。在这些情况下,每个用户都可以请求锁定文件。还有一个svn属性(needs-lock)可以应用于文件,这些文件在结帐时使它们只读,并在锁定时进行读写,这样您就可以记得在编辑之前请求锁定。
See the chapter on locking in the svn book.
请参阅有关锁定svn书籍的章节。
#2
0
Wouldn't that defeat one of the purposes of a concurrent versioning system like SubVersion? Generally, you'll check out a block of files, but the server doesn't know whether anyone is editing those files. Why not allow another user access to those files and deal with the results if a conflict emerges?
难道这不会破坏像SubVersion这样的并发版本系统的目的之一吗?通常,您将检出一个文件块,但服务器不知道是否有人正在编辑这些文件。为什么不允许其他用户访问这些文件并在出现冲突时处理结果?