SVN不再在所有子文件夹中写入.svn吗? [英] SVN no longer writes .svn in all sub-folders?
问题描述
我最近将SVN客户端从1.6.9升级到1.7.2，并转换为新格式后，我注意到不再有.svn每个子文件夹.对于我的特定配置，这不是很方便.
I recently upgraded my SVN client from 1.6.9 to 1.7.2 and after converting to the new format, I noticed that there is no longer a .svn every sub-folders. For my particular configuration this is not very convenient.
是否可以撤消此操作或恢复到旧行为，即CO中的每个子文件夹都有一个.svn?
Is there a way to undo this or revert to the old behavior where each subfolder from a CO would have a .svn ?
推荐答案
Subversion 1.7完全重写了Subversion的工作副本元数据管理系统，其代码为WC-NG.旧系统是Subversion编写的第一部分，随着时间的推移，维护和扩展变得越来越困难. WC-NG旨在立即改善性能，同时还可以实现许多将来的功能增强.
Subversion 1.7 features a complete re-write of the working copy metadata management system of Subversion, code named WC-NG. The old system was one of the first parts of Subversion written, and over time had grown difficult to maintain and extend. WC-NG is intended to provide an immediate performance improvement, while also enabling many future feature enhancements.
Subversion 1.7中引入的更改的关键特征是将工作副本元数据存储集中到一个位置. Subversion 1.7工作副本在工作副本的根目录中只有一个.svn目录，而不是工作副本中每个目录中的.svn目录.此目录(除其他外)包括一个由SQLite支持的数据库，该数据库包含该工作副本所需的所有Subversion元数据.
A key feature of the changes introduced in Subversion 1.7 is the centralization of working copy metadata storage into a single location. Instead of a .svn directory in every directory in the working copy, Subversion 1.7 working copies have just one .svn directory—in the root of the working copy. This directory includes (among other things) an SQLite-backed database which contains all of the metadata Subversion needs for that working copy.
即使数据以结构化格式存储，数据之间的关系也很复杂.我们强烈建议外部工具不要修改此数据库中保存的数据，因为这种修改很可能会导致工作副本损坏.
Even though the data is stored in a structured format, the relationships between the data are complex. We highly discourage external tools from modifying the data held in this database, as such modification is likely to result in working copy corruption.
这篇关于SVN不再在所有子文件夹中写入.svn吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
