[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Option file date

From: Johan Corveleyn <johan.corveleyn_at_uz.kuleuven.ac.be>
Date: Tue, 7 Jul 2009 11:04:16 +0200

> From: Hari Kodungallur [mailto:hkodungallur_at_gmail.com]
> There is an option in the client's config file to use the commit
> time of the file (The option that is: "use-commit-times=yes". This
> is commented out by default]. When you use this option, the checked
> out file will have the timestamp of the file at the time it was
> checked in and not when it was checked out / updated. (I hope that
> is what you meant by "file date will be the date of file").
>
> This is, however, a client config. AFAIK there is no global server
> option for this.
>
> -----Oorspronkelijk bericht-----
> Van: Ramachandran, Vishwanath(IE10)
>
> Thanks for the reply. We use Tortoise svn, where do I find the use-
> commit-times=yes
>
> Since there is no global server option for this, where do I find
> the use-commit?

Go to Settings | General, and click on Edit next to "Subversion configuration file". Then you can edit the config file.

Remember that this is a client setting, so it's only active for the specific client on which you change the config file.

Also, just to be clear on this: use-commit-times=yes makes sure you get that the files' times are set to the *last committed* timestamp. This is not the same as the time when the file was last modified by the author (last modified != last committed). If you really want the last-modified time, you'll have to wait until issue #1256 gets resolved: http://subversion.tigris.org/issues/show_bug.cgi?id=1256

Regards,
Johan

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2368692

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-07 11:05:50 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.