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

Re: Tags vs. labels

From: Res Pons <pons32_at_hotmail.com>
Date: 2006-03-31 19:08:16 CEST

I don't understand why you'd want your users to get the latest tags when in
fact the latest tag is usually the latest HEAD state of the trunk?! A Tag
is supposed to be for a build/release engineer to preserve the pristine
state of a release or working build, should it be necessary to whip up a
build on the fly. And if you check out a tag, you will invite trouble as
you developers MUST remember to do an svn switch as to not check back into
the tag inadvertently or otherwise what's the purpose of a tag if its static
state is going to be changed? Why can't you use branching?

----Original Message Follows----
From: Dripple <dripple2@laposte.net>
To: karg@quipsy.de
CC: users@subversion.tigris.org
Subject: Re: Tags vs. labels
Date: Fri, 31 Mar 2006 08:36:47 +0200
MIME-Version: 1.0
Received: from tigris.org ([204.16.104.146]) by bay0-mc6-f3.bay0.hotmail.com
with Microsoft SMTPSVC(6.0.3790.1830); Thu, 30 Mar 2006 22:37:26 -0800
Received: (qmail 20371 invoked by uid 5000); 31 Mar 2006 06:37:15 -0000
Received: (qmail 20339 invoked from network); 31 Mar 2006 06:37:14 -0000
X-Message-Info: JGTYoYF78jFFMnJg1vsvWIlO6pZzb7VcQyPM0CbwcM8=
Mailing-List: contact users-help@subversion.tigris.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
list-help: <mailto:users-help@subversion.tigris.org>
list-unsubscribe: <mailto:users-unsubscribe@subversion.tigris.org>
list-post: <mailto:users@subversion.tigris.org>
Delivered-To: mailing list users@subversion.tigris.org
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013)
X-Accept-Language: fr, en
References: <442CC5E3.3080601@laposte.net> <442CCB84.5070309@quipsy.de>
Return-Path: users-return-47264-pons32=hotmail.com@subversion.tigris.org
X-OriginalArrivalTime: 31 Mar 2006 06:37:26.0923 (UTC)
FILETIME=[938CADB0:01C6548D]

And if I want to label each and every commit, is it possible to "tag" any
working copy instead of committing to the trunk ? If it is possible, one
other question is : how others user will get the last "tagged" version,
instead of the one in the trunk ?

Markus KARG a écrit :

>Dripple schrieb:
>
>>Hi,
>>
>>I'm currently reading the SVN User Book. I found that SVN somehow has a
>>"tag" feature, which is in fact a subdirectory of a project. My point is
>>to manage differetn revisions of a file, directory, or mixed with my own
>>named revision numbers. For exemple, instead of having revision nr. 123,
>>I'd have revision nr. V1.2_0003.
>>
>>That's why I'd like to have labels to do it... And then develop a script
>>that allows users to load a revision using labels instead of revision
>>numbers...
>>
>>Is it possible ?
>>
>>Thanks for any comment.
>>
>>Dripple
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>>For additional commands, e-mail: users-help@subversion.tigris.org
>>
>Dripple,
>
>you don't need to write a script, you can just use svn's CLI. All you need
>to create your own "label" is the svn copy command. If you want to retrieve
>the "labelled" version, just use the "label"'s URL instead of the trunk
>URL. You'll find examples for both in the SVN book.
>
>Markus

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

_________________________________________________________________
Don’t just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 31 19:10:00 2006

This is an archived mail posted to the Subversion Users mailing list.

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