为什么主干更新到分支的头部修订？
Why is trunk updating to branch's head revision?
我正在使用 Tortoise svn。
当我更新 svn trunk 目录时，它会更新到 svn 分支的 head 修订版。
有人知道为什么会这样吗？
当您更新工作副本时，它会更新到 HEAD 修订版，除非您指定特定的修订版。
svn update brings changes from the repository into your working copy. If no revision is given, it brings your working copy up to date with the HEAD revision.
由于修订号适用于整个存储库，因此在更新主干时看到最新修订是完全正常的吗？
Unlike most version control systems, Subversion's revision numbers apply to the entire repository tree, not individual files. Each revision number selects an entire tree, a particular state of the repository after some committed change. Another way to think about it is that revision N represents the state of the repository filesystem after the Nth commit.
我正在使用 Tortoise svn。
当我更新 svn trunk 目录时，它会更新到 svn 分支的 head 修订版。
有人知道为什么会这样吗？
当您更新工作副本时，它会更新到 HEAD 修订版，除非您指定特定的修订版。
svn update brings changes from the repository into your working copy. If no revision is given, it brings your working copy up to date with the HEAD revision.
由于修订号适用于整个存储库，因此在更新主干时看到最新修订是完全正常的吗？
Unlike most version control systems, Subversion's revision numbers apply to the entire repository tree, not individual files. Each revision number selects an entire tree, a particular state of the repository after some committed change. Another way to think about it is that revision N represents the state of the repository filesystem after the Nth commit.