Ryan Schmidt wrote:
>
> On Feb 27, 2007, at 08:37, Frans Knibbe wrote:
>
>>> Only if you put the file time in a custom property which you restore
>>> after checking out.
>>
>> Yes, I thought about that too. That way, the file modification time
>> would not be really lost but just stored in a different way. And if
>> something like a post-checkout hook existed I could even reset the
>> file time of the working copy. But such a hook does not exist....
>
> Not only is there no post-checkout hook [1] but hooks run on the
> server, and it sounds like you are asking for hook that runs on the
> client. No Subversion hooks currently run on the client, so this would
> be much work to implement. And I believe that because of potential
> platform differences and differences in installed scripting languages
> on clients, client-side hooks are a very prickly proposition.
>
> Sounds like you should just be writing a wrapper script to go around
> "svn checkout", which itself calls svn checkout, then mucks with the
> modification dates of the checked-out files in whatever way you like.
>
>
> [1] I did write a script to implement a post-checkout hook, but it is
> a server-side script, of course; it does not do anything on the client:
> http://www.ryandesign.com/svnhookdispatcher
Thank you for your suggestions. I have done some testing and I think I
will choose the option to set the system time to the file modification
time before each commit. It is a simple solution and I think it is
sufficient for our purposes. All migrated files will have recorded
commit times equalling file modification times. All future changes will
just have a commit time, but this time will not differ much from the
file modification time if users don't wait too long before comitting.
Cheers,
Frans
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 1 15:22:17 2007