[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Need advise for branching/tagging/trunking an entirely new revision of trunk

From: Daevid Vincent <daevid_at_daevid.com>
Date: Fri, 13 Jul 2012 17:56:44 -0700

We have been building and maintaining our project for 18 months in SVN
"/mycompany/m.example.com/trunk".
Current revision is @r3881.

Now we want to re-design. This includes directory structures, files, code,
etc.

I was thinking we just want to shove everything that is now 'trunk' into a
'branch' and start with a clean slate in 'trunk'. Everyone will re-checkout
and we will re-export on the production server too. We are only 3
developers, so impact is minimal whatever we decide.

[a] is this advisable? if not, what is the proper way to do this?

[b] what would be the SVN commands to accomplish this?

[c] we've never done any branching or tagging before. We simply use SVN for
the very basics to commit, revert, archive/backup, export/checkout, etc...

We're running Subversion 1.6.16 if that matters.
Received on 2012-07-14 02:57:28 CEST

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.