On May 9, 2007, at 08:23, nikhil gupta wrote:
>> I don't have an answer for this, but I'm curious as to why you
>> wouldn't
>> just let svn (or cvs) update everything that is not current (or
>> specify
>> the time you want) in one operation.
>
> 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.
Not really... All you need is "svn up -r '{2007-05-09 23:59:59}'".
This will update your working copy to the state of the repository at
that date and time. No need to get a list of files to do the update.
Now, if you need the list of files for your build system, then,
coincidentally, the output of that "svn up" command will give you the
list of what changed, so you can just use that.
>> If you want to cut things off at midnight or something, I'd probably
>> just schedule an update on the build machine to happen then.
>
> 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.
He didn't mean "cut off" as in stop development for a time; he meant
that if you want to update your build system's working copy not to
the current version but to a version from a specific earlier time,
then you could schedule the "svn up" command to run at that
particular time.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 10 10:55:44 2007