I just started working on some changes against trunk on an SVN repo, thinking they would be somewhat small. Now, I actually am beginning to realize that I probably should have just started a new branch instead. Rather than making a branch, and then moving each individual piece into it, is there any way to make a new branch and then commit the changes in my working copy to it?
相关问题
- How can I set the SVN password with Emacs 23.1 bui
- If statements in .htaccess files, to enable passwo
- SVN+SSH checkout over VPN using tortoise SVN, Smar
- Correct procedure to use pending branch changes in
- Mercurial compared to private branches in SVN
相关文章
- Is there a version control system abstraction for
- Intermittent “SVNException: svn: E175002: Connecti
- IntelliJ Subversion Authentication Required Dialog
- TortoiseHG and hgsubversion (Windows): “no module
- Incompatible JavaHl library loaded
- Tag multiple branches in git?
- TFS vs. JIRA/Bamboo/SVN [closed]
- converting svn repo to git using reposurgeon
You can directly branch the state of your working copy to a URL with the
svn copy
command. The created branch will include the local modifications.Some gotchas:
svn update
before attempting to branch in this way.svn copy
, the working copy will be unchanged. It will still point to the trunk. It will also still show the local modifications in its status. You should first revert these modifications, whether you continue using the working copy as is or switch it to the new branch.DO NOT MAKE ANY CHECKOUT
I do it with svn 1.6.5, it works without trouble but if you are really paranoid you could do following:
What about creating a patch from your current work with
svn diff
, then making a new branch, and applying the patch to the branch withpatch -p0
?