[EMAIL PROTECTED] writes:
> mass-check was using the Last Changed Revision # from the source tree to
> figure out what version was in use, but we use the raw revision # when
> specifying nightly/weekly runs, and the two numbers are very rarely
> equal, so it gets hard to track with different numbers. just use the
> revision checked out.
The problem with this, iirc, is that this number can change as the
repository changes, even if the subset of the repo that we have
checked out, does not change:
- "svn up" updates to revision 390000 from spamassassin/trunk. (This is
the revision we want "mass-check" to report.)
- a commit occurs in someotherproject/trunk
- "svn info" reports "Revision: 390001"
--j.
> Modified:
> spamassassin/trunk/masses/mass-check
>
> Modified: spamassassin/trunk/masses/mass-check
> URL:
> http://svn.apache.org/viewcvs/spamassassin/trunk/masses/mass-check?rev=384018&r1=384017&r2=384018&view=diff
> ==============================================================================
> --- spamassassin/trunk/masses/mass-check (original)
> +++ spamassassin/trunk/masses/mass-check Tue Mar 7 13:20:48 2006
> @@ -733,8 +733,8 @@
> }
>
> while (<SVNINFO>) {
> - # Last Changed Rev: 320871
> - next unless /^Last Changed Rev: (\d+)/;
> + # Revision: 383822
> + next unless /^Revision: (\d+)/;
> $revision = $1;
> last;
> }
