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

ExportedRevision keyword

From: Martin v. L÷wis <Martin.vonLoewis_at_hpi.uni-potsdam.de>
Date: 2006-12-11 05:21:07 CET

When people export a source tree from the trunk or from a branch,
it is difficult to tell afterwards what precisely they exported
(unless there is a file that changes with every commit, and
 that has a LastChangedRevision keyword). For a regular checkout,
this data is still available, e.g. through svnversion(1) (including
the difficulties that the local tree may be modified, and may have
inconsistent version numbers).

I'd like to propose another keyword, $ExportedRevision$, which
gets set on export the revision of the tree used for the export.
On a regular checkout, this would expand to an empty string
(e.g. $ExportedRevision: $).

Then, in a build process, people could check the svnversion
output; if it is "exported", they could use the ExportedRevision
keyword. If the svnversion tool is not found, we would just check
$ExportedRevision$, if it's empty, we can't know what the tree
version is.

What do you think?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 11 05:21:29 2006

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