With use-commit-times set to yes a checkout will change the checked out
files timestamps to the last change for that file(I want that). It also
modifies the timestamp to the commit time for a revert too which causes
incorrect builds when a project is under heavy development and the
developer does not remember to touch the reverted file to update the
timestamp to now(part that I don't want). It is not always noticeable
that a file was not rebuilt without careful scrutiny because other files
could have been changed and get rebuilt.
Scenario...
1. Checkout project
2. edit file1
3. build the project with make
4. revert file1 (timestamp of file1 now changed to an old time)
5. edit file2
6. file2 gets rebuilt but file1 does not.
Building the project shows some output with make because a second file
was modified making it hard to know(without manually checking each file
that was compiled in the terminal window's back buffer and comparing it
with what you know should have been built). The binary file you just
compiled is not the correct binary.
The quick fix is to make sure and remember to touch any reverted files
but that is hard to keep up with in practice.
Because of this it would be nice if use-commit-times only modified the
timestamp of files for a checkout. From my development perspective a
revert is a change on the local file so it should get the current time
for the timestamp.
I dont want to disable the timestamp feature because it is real handy to
have an idea how old a checked out file is just by looking at the
timestamp(other people without svn can get a general idea how old files
are too).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 22 17:04:22 2005