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

Re: New User - Importing a project with active changes

From: Jean-Marc van Leerdam <j.m.van.leerdam_at_gmail.com>
Date: Tue, 5 Feb 2008 12:59:18 +0100

Hi Alan,

On 05/02/2008, Alan Saunders <ADS_at_tigersolv.com> wrote:
> My startup problem is that, starting with an empty repository, I need to
> import the existing working version of the code (as released to the client)
> into the Current and Releases. (this bit's easy, import into the Current
> (Trunk), then create a Release (Tag) from the same working copy.) Now the
> problem. How to 'import' my extensive changes into a new
> Changes(Branches)/Alan folder. (The Changes repository will contain a folder
> for each developer.)
> I have read the Subversion book, and the TortoiseSVN help from cover to
> cover, and all examples in both seem to follow the Initial
> import/checkout/change commit scenario, nothing seems to describe what I
> want to do!

You could checkout a (temporary) working copy of the entire repository
and add the branch files for developer X there. Then commit.

Repeat the process for developers Y, Z etc..

Then throw away that working copy and create a new (checkout) from
just the Current or the Changes (dev X) branch.

   // \\  @@     "De Chelonian Mobile"
  / \_/ \/._)    TortoiseSVN
 <\_/_\_/ /      The coolest Interface to (Sub)Version Control
  /_/   \_\      Check out http://tortoisesvn.net
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-02-05 12:59:25 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.