Either 1.) we are missing something in what you are trying to do, or 2.)
Subversion just won't do what you are asking at this time. When you say
you want a tag to apply to the whole source tree, you are referring to
something more like a label such as what came with StarTeam or VSS and
the like where it is more like an attribute assigned to all files at
some point in time. I'm far from an advanced user of the system, so I
am not aware of any attributes that Subversion has that can do this for you.
The tags are nothing more than directories. They have no 'real'
functionality beyond appearing to be a directory within a larger tree,
although because copies are 'cheap' in Subversion, these directories are
only pointers to the code as some point in time. From what I gathered,
Lorenz idea was about as close as anything else to giving you what you
want. It's not a requirement to use branches, so this should work...
So - that said, what exactly about this doesn't work? What is your
specific reasoning for wanting to do this? This may help others reading
this to chime in and help out.
Regards,
Frank
Olivier Sannier wrote:
> Lorenz wrote:
>
>> Hi,
>>
>>
>>
>>> [...]
>>>
>>
>>
>> what about
>>
>> /trunc
>> /libs
>> /somelib
>> /someotherlib
>> /project_one
>> /project_two
>> /tags
>> /sometag
>> /libs
>> /somelib
>> /someotherlib
>> /project_one
>> /project_two
>>
>>
> Yes, thanks, that's the recommended way, but I would like to avoid
> having the "trunk" directory, hence the need to "exclude" tags from a
> regular checkout.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 1 13:52:05 2005