AL> On 3/1/07, Neville Franks <firstname.lastname@example.org> wrote:
>> I am baffled by the use of Date's in TSVN, which is likely a
>> Subversion issue, not a specific TSVN issue.
>> When I commit a file it uses the current system date/time for the file
>> date in the repository and not the actual file date/time as it is for
>> the file in the 'working copy'.
>> If I then Checkout the file to another PC or folder or Update it on
>> another PC its date/time isn't as per the original 'working copy' file
>> This means the exact same file on different PC's have different time
>> stamps, which messes up backups that utilize time stamps, and can mess
>> up build processes.
>> I've done some searching for info on this, but so far I've come up
AL> It's fairly well-known and documented (and often discussed to death on
AL> the Subversion mailing list) that Subversion doesn't maintain
AL> last-modified dates as part of the versioned data. At one time there
AL> was a series of patches to do this and some other metadata, but I
AL> don't think it's maintained anymore.
AL> You can configure your client(s) to set the date/time of items in your
AL> WC to the time the files were committed by setting use-commit-times =
AL> yes in the [miscellany] section of your config file.
AL> Why are your backup tools (at least on Windows) relying on date/time
AL> to decide whether a file has been updated, instead of looking at the
AL> archive bit?
AL> If your build process is this sensitive to dates, I'd start worrying
AL> about how reliably it builds what you think it's building. The build
AL> tool I'm using (AnthillOS, for Java web apps) does a fresh checkout as
AL> its starting point for each build, so everything is always known to be
AL> clean from Subversion (nothing locally modified).
Andy, Thanks for the prompt reply. I figured that this was probably
how it works, but it just seems completely brain dead to me. I fully
appreciate that there can be tricky issues handling time stamps across
PC's and time zones, but at least give me the option to try and use
the files last-modified time stamps.
My previous Version Control System handled this as I would expect, so
this has come as quite a nasty shock. I really don't want the exact same
files on different PC's to have different time stamps, and I can't see
that I'm being unreasonable.
Backup programs preserve time stamps for a good reason and its like
saying they might as well not bother.
If I'd been aware of this and other issues I mentioned on my blog post
I probably would have stayed with my previous VCS.
Neville Franks, Author of Surfulater and ED for Windows
Soft As It Gets Pty Ltd, http://www.surfulater.com - http://www.getsoft.com
Victoria, Australia mailto:email@example.com
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Mar 1 12:20:35 2007