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

Re: SVN equivalent for CVS history

From: Nathan Kidd <nathan-svn_at_spicycrypto.ca>
Date: 2007-05-09 17:08:29 CEST

Méresse Christophe wrote:
> nikhil gupta wrote:
> > Thanks for the reply.
> > My actual target is to compile only those solutions which were
> > updated the previous day. For this I need to have the list of those
> > files first. Apart from this, my organization has development, both
> > at US and India. So, its like the development is on round the clock
> > & we can not cut things off.
> What you need is probably
> svn log -r {2007-05-05T00:00}:{2007-05-05T23:59} -v -q URL
> Then, pipe the command on a grep (for instance) to keep only the files
> pathes.

Or to avoid the grep, use:
  svn diff --summarize -r {2007-05-05T00:00}:{2007-05-05T23:59}

But Nikhil, I think you're approaching this problem from the wrong angle.

If you have a requirement to build only solutions that have changed,
then it should be the job of your build system to have proper
dependencies and only build what has changed, based on what is on your
disk (not parsing update logs).

SVN revisions become meaningless in your project if you have to say
"This build was made from whatever projects we felt like updating and
building at such-and-such a time". A more robust approach is to 'svn
up' for every build (no room for missing anything, your tree is in a
consistent state at a definite revision number), then teach your build
system to build targets only when sources have changed.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 9 17:06:45 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.