I think you can use svn log to fetch these informations. Also svnstat is
useful . http://www.statsvn.org/
We uses our homeproduct for controling the commits & for review processes
and metrics on it.
One thing which i would suggest you that bring some policy for a commit like
it should have some valid reason (issue id) & a valid reviewer or control
over estimated time. etc. It will do a basic control over right commits .
Else its a pain when different people are following different policies.
On Wed, Jan 14, 2009 at 2:19 PM, James Green <James.Green_at_occam-dm.com>wrote:
> Hi All,
> One of the things that I have to do this year is a stack of code reviewing
> Basically we have outsourced a stack of dev work to a company in India and
> I need to make sure they are doing things as we would like and more
> importantly in a correct fashion.
> Is there a way to query an entire server (many individual repositories) for
> new/changed files?
> James Green
> Solutions Developer
> Occam Direct Marketing Ltd
> Tel: 01761233833
> Direct: 01761234716
Received on 2009-01-15 05:19:34 CET