On Jul 6, 2006, at 22:03, email@example.com wrote:
>>> Timestamp help....
>>> I am looking for SVN to allow a user to upload a repository to an
>>> server with original timestamp info and pull that orig timestamp
>>> back down? Have a program that has a bulky DB of it's own that we do
>>> not want to put into SVN. We just want to manage the sources with
>>> you pull down a working copy and then move the program's /DB
>>> preserving the original timestamp information into the path of
>>> the SVN
>>> sources, SVN has affixed the commit time timestamp and not the
>>> original timestamp.... I then fire up the program and hit the
>>> button. The program compares the timestamp of the SVN sources to the
>>> files in the DB and sees the sources as being "Newer" due to the
>>> commit timestamp so it recompiles. We cannot afford a recompile if
>>> nothing has changed except the timestamp since there is an
>>> un-deterministic nature of the compiled output. (Means we have to
>>> unnecessarily re-verify the newly compiled
>> You may want the client-side option use-commit-times. Look in your
>> client's config file.
> Hi Ryan, Tried that and to no avail..... When I pull it down I get the
> timestamp of when it was committed. Is it possible that the server can
> be configured to ignore this client side switch?
Yes, that is correct; that's what the option does. Without use-commit-
times, when you check out, the mtime is set to now. With use-commit-
times, the mtime is set to the time when the file was committed.
If you would like to keep track in the repository of the time when
the file was modified instead of the time it was committed, then
Subversion cannot do that out of the box. There is a branch of
Subversion available, called the text-time branch, that you can build
yourself which includes this feature. See:
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Jul 6 22:36:46 2006