I'll just put in my 2 cents...
Visual Source Safe has this ability. It can be configured on the
client side to set the date of files based on the time that you "get"
them, or to preserve the original timestamp.
For many things (e.g. shared 3rd party libraries that are checked in as
binaries) I want the original timestamp preserved so that I know what
version (vendors version, external to the source control system) of the
file I am linking against. Often the timestamp of the file is the only
meaningful indicator of which "version" of a particular file I have.
It is a property that is available to anyone, even end users of our
software can easily check dates to see if they have an old file or
something like that.
I remember changing my client's setting to update the file timestamps
on a checkout (with VSS) and I got several complaints from others that
they couldn't tell when things really changed because of that. In this
case things like PDF or or document files related to the product were
in the version control system and people liked to see the "real"
modification dates of those files when they were installed with the
product. Since the build system checks out the all such files before
it compiles and builds an installer, these non-source files appeared to
have changed when compared with previous installs of the product.
I wonder even, if having the modification time preserved by default for
binary files and leavving it as-is for text files makes any more sense?
It could end up doing the "right" thing more often in my specific case
at least.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 17 16:12:49 2004