Thanks all for your answers, to be short :
No the replication tools cannot be (easily) modified without reviewing the
entire architecture because :
-The tool is under the control of another team.
-It run on a central server because we just have shares on
distributed servers (no processes).
-These servers (~30) are on a WAN, and some got lowbandwidth, so
making a checksum comparison would flood the WAN.
(thats why only names and dates are checked)
So today :
-We cannot work with obsolete dates of files,
-We cannot involve the energy to modify our model in dept.
The good point is we are only at the earlyest stage of using a SCM (but we
REALLY need one).
The bad point is I missed this issue when qualifying svn. :/
"Ph. Marek" <email@example.com>
cc: Franck FD DUPUY/FR/ALCATEL@ALCATEL
Subject: Re: Subversion erase original date of files ??
> Hello all,
> I'm working with subversion to make of a WindowsXP master.
> This master is quite complex with several batch for several sites and
> countries, including several setting and drivers... so it NEED to be
> The problem is when I have imported the master in Subversion, all thes
> dates of all the files have been reseted to the initial import date.
> -> This IS a problem because some of our scripts use dates of files to
> know if the file is up-to-date. (like DLLs & Hotfixes)
> Is there is a way to make subversion keeping the original date of files
There's an issue tracker entry at
which references a patch in the mailing list archives at
I've got an updated patch which worked with 0.24-1 and _may_ be possible
apply to current versions :-/
All the patch does is
- record the mtime on commit in a property "svn:text-time"
- uses this value on "svn export" to re-create the timestamp.
(these could be done regardless of usage type, I believe)
It doesn't set the mtime on a checkout or update, as there we've had the
discussion on how to make that work with make/build scenarios ...
I believe that it should be possible to flag an working copy (or possibly
repository tree, eg. by using a property) as "preserve meta-data" - and
update or checkout should do the Right Thing (TM).
BTW: If this patch gets ported to 1.1 I'd be glad to jump to a current
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Sep 21 11:11:55 2004