Re: Stricture(sic)

Scott Pritchett wrote:
>
> My structure looks like this (enforced).
>
> Sessions
> Proj1
> bin
> doc
> Proj2
> bin
>
> If I r_click a project folder, select Branch/Tag, in the to URL add
> /Ver1. This now shows in the log of the project as a 'tagged'
> version, (a cheap-copy?), this is good. If later I do an 'Update' on
> the project Tortoise now creates a Ver1 folder under the Project and
> adds all the files/folders to it, (expensive), this is bad.
>
> I know my structure isn't 'approved' but am I doing something wrong?
> I can 'commit' many times with no mention of the Ver1 folder, but as
> soon as I 'Update' .........

Well what did you expect to happen? You have created a tag within your
project structure

     Proj1
         bin
         doc
         Ver1

If you have Proj1 checked out, then as soon as you update it will add
the 'missing' folder to your working copy.

You need to create a tags folder in the repository which is at least one
level above your normal checkout level.

Use one of the structures recommended in our manual. I can't say any
more than that because you have not told us which level is checked out
from the repository. Are you checking out individual projects, or are
you checking out Sessions?

Simon

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
--