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

Re: svn commit: rev 209 - trunk/subversion/include

From: Branko ╚ibej <brane_at_xbc.nu>
Date: 2001-10-04 19:26:21 CEST

sussman@tigris.org wrote:

>Author: sussman
>Date: 2001-10-04 15:09 GMT
>New Revision: 209
> trunk/subversion/include/svn_version.h
>* svn_version.h (SVN_VER_TAG): Brane, I have no idea how the code can
> possibly know its own revision; but I do know that seeing "M3
> (r196)" all the time is confusing newbies. And nobody wants to
> update this number before each commit. Commenting out for now.

What I actually had in mind was something like this:

    * Make the checked-in SVN_VER_TAG "development" or "prerelease",
      depending on the state of the tree.
    * When creating a development tarball,
         1. check out the tree
         2. change SVN_VER_TAG to "r$(($head_revision + 1))´┐Ż
         3. check in svn_version.h
         4. if current $head_revision is greater than SVN_VER_TAG, back
            to (2)
         5. roll the tarball
         6. change SVN_VER_TAG back to whatever it was before

For a release tarball, the process is similar, except that in (2) you
#undef SVN_VER_TAG and make sure the version numbers are right.

All of this can be done by the distrib script. It's on my list of things
to do, as a matter of fact.

(If you try out my latest Win32 binary, you'll see why the tag can be
useful. :-)

Brane ´┐Żibej   <brane_at_xbc.nu>            http://www.xbc.nu/brane/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:44 2006

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.