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

Re: Global revision keyword

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2004-10-27 16:02:23 CEST

Duncan Murdoch <murdoch@stats.uwo.ca> wrote on 10/27/2004 09:49:44 AM:

> We could standardize on a daily tag, and always build the snapshots
> from the last of those: but that would slow the release of bug fixes
> by a few hours, it would load up our log file with all those entries
> where the tag was created, and it would be inconvenient: now I do
>
> svn update
> hack, build, test
> svn commit
> upload
>
> and if we followed this scheme, it would be
>
> svn update
> hack, build, test
> svn commit
> svn switch <tag>
> build, test
> upload
>
> If I fix a bug and commit it, I'd like to do a build from my
> up-to-date source, rather than switching to a tag release and
> rebuilding from that.
>

But why do developers need or care about this information anyway? I
thought the issue was that you have a user-base that are pulling from your
repository or tarballs, and it is with those people that you need this
information? Developers could just use svnversion as part of a
build/tarball process.

If you are on Windows, there is also a nice program named SubWCRev.exe
available from the TortoiseSVN project. This is similar to svnversion,
except it will do keyword substitition in a file for you.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 27 16:03:14 2004

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.