Svn can i commit to a tag

This is a minor problem, because it just leads to a warning, not an error. IMHO going down all the way of the urlPath could solve to problem. The last occurrence of an instance of IRepositoryRoot should be used rather than the fist. This would also work for repositories regardless of the repository layout global vs. Subversion implementations should not interfere with package layouts, even if SVN keywords are used.

The concept of developing templates for OpenCms 8. But after testing, you know it's the precise combination of data you need. Time to make a snapshot. Copying one URL to another won't work here. In this case, you want to make a snapshot of your exact working copy arrangement and store it in the repository. Luckily, svn copy actually has four different uses which you can read about in Chapter 9, Subversion Complete Reference , including the ability to copy a working-copy tree to the repository:.

Other users have found interesting uses for this feature. Sometimes there are situations where you have a bunch of local changes made to your working copy, and you'd like a collaborator to see them. Your collaborator can then either check out a verbatim copy of your working copy, or use svn merge to receive your exact changes.

While this is a nice method for uploading a quick snapshot of your working copy, note that this is not a good way to initially create a branch. Branch creation should be an event onto itself, and this method conflates the creation of a branch with extra changes to files, all within a single revision. Collectives on Stack Overflow. Learn more. Why shouldn't you commit on a tag Ask Question. Asked 10 years, 7 months ago.

Active 5 years, 2 months ago. Viewed 21k times. Common sense appears to be no valid argument so I need something more substantial. Improve this question. Add a comment. Active Oldest Votes. Improve this answer. Old post, but as other might still read it I'll add my two cents: Previous answers all rely on the common sense you say the client is not responding to.

Berg A. Berg 56 4 4 bronze badges. Adrien Adrien 46 2 2 bronze badges. Pilch Pilch 1. If you don't check the externals and those externals point to a HEAD revision which might change in the future, checking out the new tag will check out that HEAD revision of the external and your tag might not compile anymore. So it's always a good idea to set the externals to an explicit revision when creating a tag. If a project that is included as an external has itself included externals, then those will not be tagged!

Only externals that are direct children can be tagged. Press OK to commit the new copy to the repository. Don't forget to supply a log message. Note that the copy is created inside the repository. Note that unless you opted to switch your working copy to the newly created branch, creating a Branch or Tag does not affect your working copy.

Even if you create the branch from your WC, those changes are committed to the new branch, not to the trunk, so your WC may still be marked as modified with respect to the trunk. You can also create a branch or tag without having a working copy.

To do that, open the repository browser. You can there drag folders to a new location. You have to hold down the Ctrl key while you drag to create a copy, otherwise the folder gets moved, not copied. You can also drag a folder with the right mouse button. Once you release the mouse button you can choose from the context menu whether you want the folder to be moved or copied. Of course to create a branch or tag you must copy the folder, not move it. Yet another way is from the log dialog.

You can show the log dialog for e.