Am 25.01.2012 16:09, schrieb Alexander Shenkin:
I do have a pre-revprop-change.tmpl hook in the repository. It contains
the code below.[...]
This file is just a template, and the error message says what the
problem is: There is no hook script to allow editing revision
properties, and the
Guten Tag Alexander Shenkin,
am Mittwoch, 25. Januar 2012 um 16:09 schrieben Sie:
I do have a pre-revprop-change.tmpl hook in the repository.
That's a template, you have to adjust it to work on windows and save
it as something usable, for example as .cmd file.
Mit freundlichen Grüßen,
Alex,
the '.tmpl' scripts in the hooks directory are there for reference purposes
only. If you want the script to be executed, it needs to be named
'pre-revprop-change' with no extension, and have execute permission.
Tony.
From: Alexander Shenkin
On 25/01/12 15:09, Alexander Shenkin wrote:
Hello,
I'm using the svn import script by Oliver Betz to retain file mtime
upon initial import
(http://svn.haxx.se/users/archive-2006-10/1345.shtml), but i'm getting
some errors. I'm hoping someone might be able to help me out.
when i run the
Thanks everyone for your replies. I ended up finding a solution for a
windows-executable pre-revprop-change.bat script here:
http://stackoverflow.com/questions/6155/common-types-of-subversion-hooks/68850#68850
now to lobby the dev team to add mtime-handling options in future
versions!
-Original Message-
From: Alexander Shenkin [mailto:subvers...@shenkin.org]
Sent: 25 January 2012 15:10
To: users@subversion.apache.org
Subject: Errors with mtime-retaining import script:
pre-revprop-change issue?
Hello,
I'm using the svn import script by Oliver Betz to retain
Hello again,
So, I've left my computer running the script below all day long. My
understanding is that it imports files one at a time, in chronological
order, setting the svn:date revision property each time to the timestamp
of the file. Thus, in my case, I end up with thousands of revisions
On Jan 25, 2012, at 14:07, Alexander Shenkin wrote:
What I *thought* this was supposed to accomplish was that, if you were
to checkout a new working version of the repository (and if you had
TortoiseSVN set file dates to the 'last commit time', or perhaps ran
svn checkout -r COMMITTED), your
Thanks for your reply, Ryan. I just ran some new tests: when I check
out a new working copy (just a small subdirectory of the repo in this
case), I get the right timestamps. And, when I delete a file in that
newly-checked-out directory and do an svn update, I also get the right
timestamp.
