Hello David,
I am not sure I understand this specific issue, as you can always get
the specific "label" (r31).
Would svn export|co -r31 ... solve the problem?
Also in svn tags should not be modified as opposed to branches (you can
write scripts if needed).
Cheers,
*Jean-Claude Antonio*
Responsable Méthodes/Outils
Arcetis,
VoilaSVN Subversion Search Engine
Tél: +33 (0)6 09 13 15 63 - Fax: +33 (0)9 59 18 24 38
Mél: jcantonio@arcetis.com
www.arcetis.com
fj a écrit :
>
> Bicking, David (HHoldings, IT) wrote:
>> I have an interesting situation where labels (rather than "tags") would
>> be handy. I want to identify a certain revision (r31) as a suitable
>> rollback point during testing. Since we're testing the functionality of
>> Subversion, we don't really care about the revisions after this stable
>> starting point. We care about whether the behavior is as expected, and
>> we might want to rollback all changes to r31 to start fresh.
>>
>> Now, this is just the current need. I can forsee where we might want to
>> identify particular revisions for the future. For example "We created
>> branch XYZ at this revision". Of course, these labels would have to be
>> something we can easilly see with a report or by looking at a property
>> history on the repository.
>>
>> Do any of you know an efficient way to get this functionality? I took a
>> quick stab at creating a custom property called "label" but it doesn't
>> seem to be what I need. When I update it, the original is then hidden
>> in history and I can't really find it in a repository browser or a
>> property list in my workspace.
>>
>>
>> --
>> David Bicking
>>
>>
>> *************************************************************************
>>
>> This communication, including attachments, is
>> for the exclusive use of addressee and may contain proprietary,
>> confidential and/or privileged information. If you are not the intended
>> recipient, any use, copying, disclosure, dissemination or
>> distribution is
>> strictly prohibited. If you are not the intended recipient, please
>> notify
>> the sender immediately by return e-mail, delete this communication and
>> destroy all copies.
>> *************************************************************************
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: users-help@subversion.tigris.org
>>
>>
> for what it's worth, I second the idea (as i have in previous
> messages) of implementing a real label feature in svn.
>
> I was a StarTeam administrator for 6 years, as well as being the qa
> director, primary software config. mgmt. authority, and I think I also
> washed a few bottles every now and then at that same gig. With
> StarTeam, we used their view-level and rev-level labeling feature
> extensively; it is quite powerful. I don't want to run-on about it,
> but if anybody has any questions about it I'll certainly try to
> elaborate. My point is, labeling, done well, can indeed be a very
> useful capability.
>
> Don't get me wrong -- SVN's a great tool, especially for the price
> (StarTeam cost a stunningly large amount of money for the number of
> licenses the organization owned), and I'm generally agnostic about
> tools -- use what I have to, use what I've got, etc., and figure out
> how to make it work. Part of the ex-military in me... but I do miss
> some of StarTeam's features, and a true labeling capability like
> StarTeam has is one of those features I miss.
>
> cheers,
> fj
>
> ---------------------------------------------------------------------
> 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 Sun Aug 26 15:35:29 2007