Greg Hudson wrote:
> > An alternative idea to reduce the sleep: track the most recent
> > timestamp.
>
> This is probably not much more complicated (it requires libsvn_wc to
> update a timestamp variable each time it stores one in the
> entries file,
> as opposed to my and Ben's idea where it would have to see a timestamp
> variable each time) and will probably save the full second in most
> cases.
What is the exact reason for this sleep? Has it something to do with
make(1) or are there additional reasons beyond make?
> This is a totally different feature; the fact that both would be using
> utimes() doesn't make them terribly related. And I would say the time
> of the last commit isn't the right answer; the right answer is a
> timestamp property set on the file (which we don't current set). That
> way you could a import a collection of files with this property set on
> each file, and a checkout would have the same timestamps--a property
> many build systems want to ensure.
This seems somewhat odd to me. Let's assume:
$ svn up -r HEAD
$ make
$ svn up -r PREV
$ make
In this example make will fail to rebuild if you change the timestamp
to the older value. Therefore it seems the best not to fiddle with the
timestamp and rely on the OS to do it right.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 14 12:58:41 2003