why tagging?

[kychan <ky...@utas.edu.au>]

I'm just thinking "why tagging". I know a tag in svn is sort of a copy of a particular revision. But I don't want this happens, all I want is to "mark" a particular revision as "something" (e.g. release 1.1.2b), and the repo should be getting bigger in size which is unnecessary I think.

So am I wrong? Any ideas?

Thank you

Re: why tagging?

["C. Michael Pilato" <cm...@collab.net>]

"kychan" <ky...@utas.edu.au> writes:

> I'm just thinking "why tagging". I know a tag in svn is sort of a
> copy of a particular revision. But I don't want this happens, all I
> want is to "mark" a particular revision as "something" (e.g. release
> 1.1.2b), and the repo should be getting bigger in size which is
> unnecessary I think.

If you copy directory, your repository will only get barely bigger.
But that said, the feature you are asking for (which in my mind is
called "revision labelling") is a common request, and I think a good
feature to have.  You can today set a custom property on your revision
that says, "My neat-O kychan-summoned name is BLARG".  It's just that
harvesting that information from the repository after-the-fact is a
trifle difficult.

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

Re: why tagging?

[Dave Neary <da...@phenix.fr>]

Hi Kychan,

kychan wrote:
> I'm just thinking "why tagging". I know a tag in svn is sort of a copy
> of a particular revision. But I don't want this happens, all I want is
> to "mark" a particular revision as "something" (e.g. release 1.1.2b),
> and the repo should be getting bigger in size which is unnecessary I
> think.
>  
> So am I wrong? Any ideas?

Tagging is, as you say "just marking a particular revision as 
something". Rather, it's marking part of the repository at a given 
revision as something.

If you follow the reccommended filesystem layout for your repository, 
you have
trunk/(files)
branches/(branch names)/(files)
tags/(tag names)/(files)

Creating a tag is simply doing an svn cp of the trunk or a branch to the 
tags directory, taking a snapshot of that part of the repository at that 
moment. The repository does get bigger, by the size of one directory 
node. And this is the smallest possible increment you can have.

Say I have
branches/1.1/stuff

and I want to make release 1.1.3. I'd just go
svn cp file://repos/branches/1.1 file://repos/tags/1.1.3
now everything in tags/1.1.3 is the same as in 1.1 (only the directory 
gets copied - this is called a shallow copy), and I can carry on 
committing stuff to branches/1.1.

To make a directory a tag, you just have to not commit any changes into it.

Cheers,
Dave.

-- 
David Neary
Phenix Engineering
110 ave Jean Jaures, 69007 Lyon

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