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

Client side hooks PATH argument

From: Peter Koves <kovesp_at_sympatico.ca>
Date: Mon, 19 Aug 2013 18:12:32 -0700 (PDT)

Perhaps I'm confused, but I expected the file passed as the PATH argument to the post-update-hook (and also the post-commit-hook) to contain a list of AFFECTED files rather than just the path(s) that the command was applied to. So for update, I expected the actually updated files to be in the list.

Is the only way to find out what was updated or committed to have a 'pre-' hook, apply 'svn st -v' to the set of paths supplied, save the output in some well known location, then repeat in the 'post-' hook and derive the set of changes by comparing revision numbers? And, this doesn't even work for commit ... I could fake it with trying to do 'svn st -u' ... but the commit may be selectively stopped from the dialog.
In any case, seems pretty inefficient and complicated when you actually have the information on hand ...

My actual application is this: I have tree which contains (among other things) some XML files. These files need to have an XML processing instruction changed on a particular system, so I'd like to do that whenever any file is updated. Then the PI has to be changed back before the file is committed.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-08-20 03:12:34 CEST

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

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