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

Re: [TSVN] directory names

From: Simon Large <simon_at_skirridsystems.co.uk>
Date: 2005-08-30 13:20:48 CEST

Peter McNab wrote:
> Simon Large wrote:
>
>> What are we trying to provide protection against? I think it is mainly
>> against someone switching their WC to a tag, then forgetting they have
>> done that and making changes which they commit to the tag instead of
>> trunk.
>
>
>
>> So this is really only important if you _do_ have a WC.
>>
> Yes. If it can happen it will and it does but since providing a release
> branch it's happening much less often, just because there is no need to
> check out an actual tag to compile from..
> A part aim of having releases, which do get checked out is to compile
> from and publish/export from etc.
>
>> Also, if you apply the property to trunk, when you create the tag the
>> property will be copied there as well.
>
>
> Not sure why one would apply the property to the trunk though. Am I
> missing something?

There are (at least) 2 ways to use properties for this:
1. A property which says 'I am a tag, don't commit to me'.
2. A property which says 'If my URL contains XXX I am a tag'.

If you take the first case, you apply the property to the tag. But you
have to do that every time you create a new tag.

If the property is applied to trunk, then every time you copy the trunk
to make a branch or tag, the property is copied there automatically. But
only when the target URL contains the property value does TSVN recognize
it as a tag.

>> To make this work in practice, the end user has to make sure the
>> property is set on the lowest level that tags will be created from,
>> but that is true of all TSVN properties.
>>
> This bit I'm not quite sure that I follow. My mental model of a project
> repository has (where applicable) paths for
> Trunk
> Branches
> Tags
> Releases
> VendorDrops
> as root paths/folders all at the same level.
>
> So applying the property <tsvn:commitwarning =...> to appropriate
> folders at that root level seems clear enough for my simple brain. (If
> there is a better strategy go with it, don't be coerced by the lowest
> common denominator brain.)

The problem is that you never check out or switch to the root /tags/
folder (unless you want to check out every tag that was ever made - how
much disk space do you have?). TSVN can only search up the WC as far as
you have checked out, otherwise it has to contact the repository to do
the search. So it will not see a property applied only to /tags/.
Simon

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Aug 30 13:20:31 2005

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

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