On Tue, Mar 07, 2006 at 09:43:38PM +0000, Justin Mason wrote:
> 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:

Yes.

>   - "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"

I don't believe that's the case unless you're running "svn info"
against the repo and not the WC.  If we specify that 390000 should be
the revision to use, and everywhere we do "svn -r 390000 up", then we
get revision 390000.  For instance:

$ svn info
Path: .
URL: https://svn.apache.org/repos/asf/spamassassin/trunk
Repository Root: https://svn.apache.org/repos/asf
Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
Revision: 383789
Node Kind: directory
Schedule: normal
Last Changed Author: felicity
Last Changed Rev: 383764
Last Changed Date: 2006-03-06 23:11:40 -0500 (Mon, 06 Mar 2006)
Properties Last Updated: 2005-12-14 21:28:23 -0500 (Wed, 14 Dec 2005)

[vorlon] [04:49 PM] [503] [~/SA/spamassassin-head] $ svn -r 383780 up
U    masses/mass-check

Fetching external item into 'rulesrc'
U    rulesrc/sandbox/felicity/70_other.cf
Updated external to revision 384023.

Updated to revision 383780.
$ svn info
Path: .
URL: https://svn.apache.org/repos/asf/spamassassin/trunk
Repository Root: https://svn.apache.org/repos/asf
Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
Revision: 383780
Node Kind: directory
Schedule: normal
Last Changed Author: felicity
Last Changed Rev: 383764
Last Changed Date: 2006-03-06 23:11:40 -0500 (Mon, 06 Mar 2006)
Properties Last Updated: 2005-12-14 21:28:23 -0500 (Wed, 14 Dec 2005)


Arguably, to specify the nightly/weekly version we could specify that
the script use Last Changed Rev as the number, but it was easier to
change mass-check to match opposed to the other way around, and in the
end the actual number we use doesn't matter as long as we're all using
the same one.

-- 
Randomly Generated Tagline:
 Professor: No fair! You changed the outcome by measuring it.

Attachment: pgpUodw07YMtG.pgp
Description: PGP signature

Reply via email to