On Sat, Aug 11, 2018 at 10:41 AM, Bo Berglund <bo.berglund_at_gmail.com> wrote:
> A collegue has put a project into our SVN server. The server is
> organized such that every project is a top level directory.
> This shall contain subdirs trunk, tags and branches.
> Trunk is where the sources for the project live.
>
> Now he has put his project sources into:
> /Projectname/trunk/Projectname
>
> What is the best way to fix this so it will reside in
> /Projectname/trunk instead?
>
> - Check out /Projectname/trunk and receive subdir Projectname
> - Move to trunk on client
> - svn mv Projectname/* ./*
> - svn ci -m "log message"
>
> Or after checkout:
> - Move to trunk/Projectname on client
> - svn mv * ../
> - mv ..
> - svn ci -m "log message"
>
> I don't want to mess up the repository, so that is why I am asking....
You can, in theory-arrange the content, ideally doing it one project
at a time. by moving the components with "mv" commands. I'd also
suggest doing the trunk, then the branches, then the tags, each as
their own distinct commit.
In practice, I may have a long-term better idea for you. Split the
projects, each into their own much smaller repository with only its
own history. This is also the only good chance you'r likely to get, to
*discard* inappropriate binary files, files that accidentally were
stored with passwords, and seriously obsolete branches.tags, or even
projects altogether.
Received on 2018-08-12 09:26:48 CEST