RE: Svn branching issue
From: Cooke, Mark <mark.cooke_at_siemens.com>
Date: Tue, 8 Nov 2016 11:24:12 +0000
> -----Original Message-----
Sorry but I think most people here will disagree with that.
> without this in place, we would never be able to achieve moving branches to
Why do you think it cannot be accessed, what have you tried?
You do not seem to understand what subversion is and how it works. The path can *never* be deleted and will *always* remain accessible at the old path (if you format the URL with a revision). Other people have suggested you read up on "peg" and "operative" revisions and have tried to explain that "delete" only removes the path from the "current" view. That is why the old paths show up in the history and why you can still see them.
The subversion book is online and comprehensive, I suggest you read through some of that, including "Peg and Operative revisions":
> In my project , the folders and branches have been created in very improper
If there is real mess you could consider "parking" the repository (keeping it to access the history if required) and creating a new repository with the required structure. How does that sound?
> now, you are saying history will still point to old location, but now that
As above, you cannot stop access to those old paths, you just need to know how to access them (using the revision syntax in the URL) or using your GUI's log browser etc. (note that the core subversion project does not include a GUI so it helps if you mention what GUI you are using and what platform you are on).
> and my quest for reorganising svn branch structure in my project will be
No, you can always reorganise the structure (and still access all the history).
> don't you guys think, it is a serious limitation which need to be overcome ?
No, the limitation you see is not actually there.
I still do not understand if you have an actual problem with something you have tried to do. Hopefully this (and Stefan's post) will help you.
~ mark c
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.