Re: How to Maintain "timestamp" in Repository & Working copy ?

On Tue, Oct 11, 2011 at 8:17 PM, Phil Pinkerton <pcpinkerton_at_gmail.com> wrote:
> On 10/11/2011 11:58 AM, Andy Levy wrote:
>>
>> On Tue, Oct 11, 2011 at 11:48, Phil Pinkerton<pcpinkerton_at_gmail.com>
>>  wrote:
>>>
>>> On 10/11/2011 10:48 AM, Tony Sweeney wrote:
>>>>
>>>> -----Original Message-----
>>>> From: Phil Pinkerton [mailto:pcpinkerton_at_gmail.com]
>>>> Sent: 11 October 2011 15:42
>>>> To: users_at_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.
>>
>> Normally, one does not have TortoiseSVN on a production server in the
>> first place. Better to use tools which can be automated cleanly
>> (command-line, etc.) for hands-off deployments.
>>
>>> [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"=""
>>
>> Note that because the setting is in HCU, it will need to be set for
>> *each user* who might be doing things on this server. This holds true
>> for setting it in %APPDATA%\Subversion\config as well.
>>
>> Settings in the registry will override %APPDATA%\Subversion
>> configuration settings (that's my experience, anyway); specifying it
>> at the command line (see my other reply) should trump both.
>>
> Too bad there is not a global way to set this

You can also set it system-wide (i.e. applying to all users on that
particular client machine), both on Windows and on *nix. On Windows,
either through the registry in
HKEY_LOCAL_MACHINE\Software\Tigris.org\Subversion\Config\Miscellany,
or in the %APPDATA% of the default user (I think).

But it's still a client-side setting, you have to configure it on each client.

See http://svnbook.red-bean.com/en/1.6/svn.advanced.confarea.html.

-- 
Johan