我如何将一个文件提交到我忘记提交的 SVN,(调整它的修订号) [英] How can I commit a file to SVN that I forgot to commit a while ago, (tweaking it's revision number)

查看:28
本文介绍了我如何将一个文件提交到我忘记提交的 SVN,(调整它的修订号)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

因此,我一直很高兴使用 Subversion 定期提交与我的大型 Visual Studio 解决方案相关的项目堆栈中的文件.

So I've been happily using subversion to regularly commit files in my stack of projects related to my massive Visual Studio solution.

有一天我决定进行 svn 导出,并且决定我需要看看我的项目在 2008 年 10 月是如何工作的.所以,我导出到我的本地文件系统,修订版 37.

I decide to do a svn export one day, and, decided I needed to see how my project was working back in October of 2008. So, I export to my local file system, revision 37.

当我去编译项目时,不知何故有 2 或 3 个文件在 10 月份被忽略了.假设他们直到第 99 版才提交,或者更好的是,他们根本没有提交.

When I go to compile the project, somehow there were 2 or 3 files that got overlooked way back in October. Let's say they didn't get committed until revsion 99, or better yet, they're still not committed at all.

有没有办法调整文件上的提交编号,使其与您想要的正确修订版相匹配?因此,如果我重新导出修订版 37,我会在 Visual Studio 中获得正确且有效的解决方案吗?

Is there a way to tweak the commit number on a file, so that it gets matched up with the correct revision that you meant for it to have been? Thus, if I re-export revision 37, I'll get a correct and working solution in Visual Studio?

推荐答案

并非如此.Subversion 修订号适用于整个源代码树.如果您能够对已提交的修订进行更改,那将破坏更改管理的想法.

Not really. Subversion revision numbers apply to the entire tree of source code. If you were able to make changes to a commited revision, that would destroy the idea of change management.

您可以做的是从修订版 37 创建一个分支,然后对其进行更改.这将创建一个新修订版,例如 100.然后您可以提交该修订版,您将拥有您正在寻找的修改后的修订版 37.

What you can do is create a branch off of revision 37, and make changes to that. This will create a new revision, say 100. You can commit that then, and you will have your modified revision 37 that you are looking for.

这篇关于我如何将一个文件提交到我忘记提交的 SVN,(调整它的修订号)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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