RE: Tags

> In our project we have this structure in the trunk.
>
> trunk/
> Algorithm/
> Common/
> Modules/
> Module1/
> Module2/
> Module3/
>
> We want to make a tag on either the modules or at functions (that contain
> several modules).
> When we creates a tag for a module, we just to have that module folder in
> the tag, as shown below. For tagging the funktions would we like to merge
> the tags from the modules to a new tag that includes those modules.
>
> tags/
> Module1/
> ver 1.0/
> Common/
> Modules/
> Module1/
> Module2
> ver 1.0/
> Common/
> Modules/
> Module2/
> Funktion1
> ver 1.0/
> Common/
> Modules/
> Module1/
> Module2/
>
> Is it possible to do it this way and how if possible how should we do.

Sure you can do it that way. You can copy /trunk/Algorythm/Modules/Module1 to /tags/Module1/ver 1.0 but I don't see how you can get the Common/ and Modules/ into that tag. You would have something after your tag that looks like:

tags/
        Module1/
                ver 1.0/ (this would contain whatever the contents of /trunk/Algorythm/Modules/Module1 is at the time you tagged it)
                ver 2.0/
        Module2/
                ver 1.0/
        Funktion1/ (not sure what this is??? There is no function path in trunk)
                ver 1.0/
                        Common/
                        Modules/
                                Module1/
                                Module2/

I think what is normally suggested is to have trunk/, branches/, tags/ at the level where you want to version your system.

So, you could do something like:

/
   Algorithm/
          Common/
                 trunk/
             tag/
             branches/
          Modules/
               Module1/
                  /trunk
                  /tags
                  /branches
               Module2/
                  /trunk
                  /tags
                  /branches
               Module3/
                  /trunk
                  /tags
                  /branches

But... possibly better, I don't know your whole app is to not nest this stuff... have something like:

/
   Common/
      trunk/
      tag/
      branches/
   Algorithm/
      Modules/
         Module1/
            /trunk
            /tags
            /branches
         Module2/
            /trunk
            /tags
            /branches
         Module3/
            /trunk
            /tags
            /branches

then for your projects that use common of are module you can use externals so that when you check-out you get the correct development file system.

BOb

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2461178

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-03-17 17:34:54 CET