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

Re: svn copy WC->URL conflict

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Fri, 21 Nov 2008 13:10:17 +0000

2008/11/21 Laurent Fournier <lfournie_at_rockwellcollins.com>:
> Stefan Küng <tortoisesvn <at> gmail.com> writes:
>>
>> You have to find a different way to get your working copy. Updating
>> individual files to non-HEAD revisions is a bad idea.
>>
>> Instead of asking here why something doesn't work, tell us what you want
>> to achieve first (i.e., tell us your workflow, not the specific steps
>> you wanted to do).
>>
>> Stefan
>>
> Thanks Stefan,
>
> Maybe am I missing something because I am coming from CVS Word !
> My requirement is simple and frequent in Software Industry.
> I need to make a tag (or a branche) with elements either
> - coming from the head
> - coming from old revision
> - not present for that tag
>
> The build released does not match exactly any old build of the trunk.
> I was using the SVN copy WC->URL do to that but is there another way ?
>
> With CVS, this was easy to attach a tag to any element (head or not) and
> elements not tagged were not present in the release.
>
> Thanks for helping me achieving the same result.

You might want to ask the same question on the users _at_
subversion.tigris.org mailing list, as it is not TSVN-specific. You
will get a much wider audience there, so maybe someone there has found
a way of working this way.

Simon

-- 
:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
Received on 2008-11-21 14:10:33 CET

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.