Whole tree up to date before committing

[Matthew D. Fuller]

On Fri, Oct 23, 2009 at 03:43:42AM +0200 I heard the voice of
Óscar Fuentes, and lo! it spake thus:
> 
> The problem is that, on the project I'm talking about, there is a
> policy that requires that you can't commit changes to the master
> branch (trunk) without checking that it builds and running the test
> suite.

But, you're ending up with the exact same result as you have now with
svn.  You mean that just because the dev actually RAN update and
nothing conflicted, as opposed to the VCS internally seeing that
nothing conflicted and doing its own in-memory pseudo-update, the
dev's burden changes?

I'd send you a solution for that, but it's probably cheaper to buy a
crowbar locally...



-- 
Matthew Fuller     (MF4839)   |  fullermd at over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
           On the Internet, nobody can hear you scream.