On 10/11/2011 10:48 AM, Tony Sweeney wrote:
-----Original Message-----
From: Phil Pinkerton [mailto:pcpinker...@gmail.com]
Sent: 11 October 2011 15:42
To: users@subversion.apache.org
Subject: How to Maintain "timestamp" in Repository& Working copy ?
I have a request to keep the "commit" timestamps associated with the
file in the working copy the same.
Is that possible ? most users have their working copy on a Windows OS ,
Subversion Server is on a Unix Server ( not that that matters ).
Is there a parameter in TortoiseSVN perhaps ?
-----------------------------------------------
In the TortoiseSVN settings menu, "General" section, there is a setting
'Set file dates to the "last commit time"' -- is that perhaps what you
want?
Tony.
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1410 / Virus Database: 1520/3943 - Release Date: 10/07/11
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
So what I found looks like I'll need to mess with the client side
register parameters? , not nice on a production server.
[HKEY_CURRENT_USER\Software\Tigris.org\Subversion\Config\miscellany]
"#global-ignores"="*.o *.lo *.la #*# .*.rej *.rej .*~ *~ .#* .DS_Store"
"#log-encoding"=""
"#use-commit-times"="" < ------------------- Set this to yes and drop
the comment I suppose will do the trick
"#no-unlock"=""
"#enable-auto-props"=""
use-commit-times
Normally your working copy files have timestamps that reflect the last
time they were touched by any process, whether your
own editor or some svn subcommand. This is generally convenient for
people developing software, because build systems often
look at timestamps as a way of deciding which files need to be recompiled.
In other situations, however, it's sometimes nice for the working copy
files to have timestamps that reflect the last time they
were changed in the repository. The svn export command always places
these “last-commit timestamps” on trees that it produces.
By setting this config variable to yes, the svn checkout, svn update,
svn switch, and svn revert commands will also
set last-commit timestamps on files that they touch.
