RE: New User - Importing a project with active changes

Hi Jean-Marc,
I was going to ask for more details, You have to appreciate that svn/TSVN
isn't second nature to me (nor will it be for a while). However, Lorenz has
provided this. I think I know which way to go now. All is not lost if I get
it wrong, as I said in my original message, I'm starting from an empty
repository, so I can always delete it and start again!

My current plan:
copy my (release) files into the Current folder of a subdirectory organised
as
Current
Changes
Releases
Import the folder tree into the root repository.
Check out a working copy of the current folder
svn copy this wc into a releases/Version 1 & commit
svn copy this wc into a changes/Alan & commit
switch wc to changes/Alan
copy my modified (quite extensive) changes into this working copy

Now.. last question (for now)
Is there an SVN or TSVN command to migrate the changes into the repository
en bloc, or will I have to manually add the new files, and commit the
changed ones?

Regards .. Alan

And thanks all for your assistance.

-----Original Message-----
From: Jean-Marc van Leerdam [mailto:j.m.van.leerdam_at_gmail.com]
Sent: 05 February 2008 11:59
To: users_at_tortoisesvn.tigris.org
Subject: Re: New User - Importing a project with active changes

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.

--
Regards,
Jean-Marc
----------------
    ___
   // \\  @@     "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
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.19.20/1259 - Release Date: 04/02/2008
20:42
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org