I have a website which has not been under version control; I am moving
it to a new server, and putting it under version control with
subversion. This is my first time using svn, and I have been enjoying
it very much.
However, I am having a problem arising from the fact that svn does not
update the timestamps on my files. I have, in the past, used timestamps
as critical metadata (to see what articles are the ones most recently
uploaded or modified). Of course, when I save these files in a
repository and then check out that repository, the timestamps are incorrect.
Right now, the best approach I can think of would be to save the
timestamps as a property of the file each time (before I commit any
changes) and then, when I update any other copies, I would have to
manually set the timestamps to match the property.
Q1) Will svn get confused if I change the timestamps on checked-out
files to some time in the past? Of course, I won't back-date any
modified files...so modified files will certainly look newer than when
they were checked out, and svn will know to look at them for changes.
Q2) Does anybody have any scripts to help with this process, to save me
a little time?
Q3) Can I configure svn to automatically run a script, on the working
copy side, just before each commit, and then run a different script,
again on the working copy side, just after each checkout or update?
I know, I could just query the svn properities on each file and
directory each time that I need to look things up. But I think you'll
agree that it is undesirable to have to look up svn properties on 1000s
of files over and over again. I would much rather be able to do "ls
-trd *" as I have been doing in the past.
My other solution, of course, could be to redesign the site...I've been
pondering doing just that, but hope that I don't have to do it yet, just
to make site work well with svn.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Mar 21 07:58:21 2005