# Re: Possible Post-update issue?

From: Jeremy <jswigart_at_gmail.com>
Date: Fri, 8 Aug 2014 20:37:15 -0500

That's unfortunately not as useful as i had hoped. Would it be possible to
get that hook extended officially with a temp file that contains the
updated files so that it can act as the recieving end version of
pre-commit? I have a precommit script that updates an sqlite database with
file modification times since I have need to synchronize that information,
and I was hoping to use the post update in order to narrowly update the
local modified time of files after the update from the database. I can work
around the issue, but had hoped not to have to.

On a related note, I think the PostUpdate script example is out of date
with the parameters

Though it would be really nice to have that last updates file parameter.
Does this script reference a parameter that used to be there but isn't
anymore and was removed for some reason?

Anyways thanks for the information.

On Aug 8, 2014 12:22 PM, "Stefan Küng" <tortoisesvn_at_gmail.com> wrote:

> On 08.08.2014 05:55, Jeremy wrote:
> > I have a post update hook set up in order to get the list of files that
> > have been updated in a given update. If I perform the update on a
> > folder, such as the root folder of which my hook is configured, the hook
> > only recieves the path to the folder, and not a list containing the
> > specific files that have been updated under that folder. This seems
> > wrong. I would imagine the post-update log should ideally contain the
> > explicit list of items that are updated, otherwise the pathsfile loses a
> > big chunk of its usefulness of being able to tell via this post update
> > hook which specific files have been updated, similar to how the
> > individual 'dirty' files are provided to the precommit hook.
> >
> > Is this a bug?
>
>
> No, that's by design.
> The docs clearly state that the params passed to the hook script are:
> PATH DEPTH REVISION ERROR CWD
> and PATH is:
> A path to a temporary file which contains all the paths for which the
> operation was started.
>
> again: "for which the operation was started".
>
>
> If you really need those paths, maybe you can parse the action log file
> located in %localappdata%\TortoiseSVN\logfile.txt
>
> Stefan
>
> --
> ___
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest interface to (Sub)version control
> /_/ \_\ http://tortoisesvn.net
>
> ------------------------------------------------------
>
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3086437
>
> To unsubscribe from this discussion, e-mail: [
> users-unsubscribe_at_tortoisesvn.tigris.org].
>

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3086472

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].