On Sun, Aug 12, 2018 at 4:46 AM, Bo Berglund wrote:
> On Sun, 12 Aug 2018 03:26:38 -0400, Nico Kadel-Garcia
> wrote:
>
>>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
On Sun, Aug 12, 2018 at 3:26 AM Nico Kadel-Garcia wrote:
> 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
On Sun, 12 Aug 2018 03:26:38 -0400, Nico Kadel-Garcia
wrote:
>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
On Sat, Aug 11, 2018 at 10:41 AM, Bo Berglund 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
Bo Berglund wrote on Sat, 11 Aug 2018 16:41 +0200:
> 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
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
