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

Re: release stamping (not revision stamping) in the SVN world?

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-05-28 16:53:21 CEST

Alexis Huxley <ahuxley@gmx.net> writes:

> So, should I rearrange my sources to be stored under /trunk like this,
> so that I can later make tags with the command line above?:

As cmpilato already pointed out, you can index your repository by
branch, rather than by project. It doesn't matter.

Actually -- the important thing to remember here is that there *is* no
policy at all. A tag is just a regular directory, created via "cheap
copy". Organize your repository however you wish; the distinction
between a tag, branch, and directory is only in your mind. Hopefully
your repository structure will remind you how you want to think of

> I am aware that I can put '$Header'-like strings in files stored under
> SVN, but surely - at checkout time - those will be expanded to
> something that doesn't comtain the "1.0" (or whatever) that I use
> when tag the release with the "scn cp" command above?
> So, in the SVN world, how does one 'brand' ones sources with a
> release ID?

The $Revision$ keyword has nothing at all to do with the 'branding' of
your sources. Take a look at how the Subversion project does it: we
manually increment the software release numbers in our svn_version.h
header whenever we hit a new milestone. If you want, you can make a
tag as well.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 28 16:56:49 2002

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

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