> On 9/23/2010 11:08 AM, Bob Archer wrote: > >> Hi subversion list! > >> > >> I would like to move a whole project to another name. Let's say, > I > >> have > >> the project right now with a name called "hello", and I would > like > >> to > >> move its name to "world", which commands would I have to issue? > >> Afterwards each user should be able to check it out with this > new > >> name > >> "world", not anymore with the repository-name "hello". > >> > >> Oh, and by the way all previous check-ins should still be > >> accessible, so > >> I don't want to create a new repository and copy all files and > >> afterwards delete the old one, but simply rename it. > >> > >> Thanks for every hint in advance. > > Do you want to rename a "project" which I take to mean a folder > in your repository. Or do you want to rename the repository? > > > > BOb > > > Bob, > I figured he uses a repo for each project like I do. The subject > line says "Rename svn-repository".
Yes, but some people don't correctly use the terms "repository" and "working-copy" calling WC the repository most often on these lists. > > I use a repo for each project for this reason and many others. I > have found that so many of the problems that people have with some > of the more complicated svn commands don't exist with project > specifc repos. Perhaps the biggest benefit is that the "global" > revision numbers become a non-issue. I have never had any problems > with merging trunk to branch or branch to trunk and I still use the > techniques that were reccomended back in 1.1. > > I would like to see a discussion of the pros and cons of single > repo vs. project specific repos. > I'm sure there are several treads on the svn list about that topic. I think there is also a section in the docs that discusses it. Yep, here it is: http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.reposadmin.planning BOb
