Timestamp Frustrations

I am curious if anyone else has solved this problem. I asked about it
many months ago and no one had.

I am managing (more like, attempting to manage) a single-developer web
project with svn. The use of timestamps is embedded in my work style
and practice in a number of ways, including simply looking at what I've
changed lately, and routine copying of changed files between machines
based on date.

I attempted to write a wrapper script for the most common svn commands
which properly handles setting a timestamp property for each file when
it is added to or updated in the repository, then retrieving that and
using touch to set the file time when the file is checked out. However
this is incomplete at best (I keep discovering places where svn touches
the files that I hadn't thought of, and having to reconstruct timestamp
data), and it's cumbersome to maintain and use.

I realize that in parallel development you need the timestamp to
reflect the last commit or last checkout etc., for eample to make
builds work properly when other people's changes come into a local
working copy. But in a single-developer environment sometimes this
approach causes the loss of valuable information about the time the
file was actually last modified.

Has there been any thought to allowing svn to preserve the file
timestamp which reflects the normal OS meaning -- time of last
modification to the content -- instead of time of last version control
action or time of last commit? Anyone have a simple, reliable way to
do this now?

I am doing this work on Windows but the concerns are not OS-specific
since file timestamps generally have the same meaning in most typical
OS's.

Thanks,

--
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org