如何处理 SVN 中代码的重大结构变化？
我的 SVN 中的 trunk 下有一个项目。过去两个月我一直在研究它，它的状态很稳定。现在我想完全改变我的代码的组织或结构方式，保持业务逻辑的实现相同。我还想将代码的当前状态存储在某个地方。除了主干之外，我的存储库中还有标签、分支和发布文件夹。
我想知道处理这种情况的最佳方法是什么。我有点担心，因为如果我只是为我的旧代码创建一个标签，它不会创建完整的副本，但会创建指向主干中可用代码的链接，我最终将完全更改它。
I have a project which is under trunk in my SVN. I have been working on it for last 2 months and its in stable state. Now I want to completely change the way my code is organized or structured keeping the implementation of the business logic same. I also want to keep the current state of my code stored at some place. I have tags, branches and releases folder in my repository apart from trunk.
I want to know what is the best approach to handle this scenario. I am little worried because if I just create a tag for my old code than it will not create a complete copy but will create links to the code available in trunk which I eventually going to change completely.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您无需担心此“链接” subversion 会将您的文件复制到标签文件夹中。在内部，它不会复制这些文件，因为它们已经在您的存储库中，但 subversion 标签是副本，不是链接。
另请记住，该标签指向源代码的特定修订版，因此即使您想遵循此链接类比，该链接也将始终指向修订版和旧修订版永远不会在颠覆中改变。
因此，请继续根据需要更改源，但在开始之前创建一个标签。这样你就可以随时回去。
You do not need to worry about this "links" subversion will copy your files into the tags folder.internally it does not duplicate these files, as they are already in your repository, but subversion tags are copys, not links.
Also keep in mind that the tag is pointing to a specific revision of your sourcecode, so even if you want to follow this link analogy, the link will always point to a revision and an old revision will never change in subversion.
So go ahead and change the source as you like, but create a tag before you start. In this way you can always go back.