Garth Snyder wrote:
> This feature has been working really well for me. But I notice a couple of
> design issues (current as of 13302).
> First, execution of the post-update hook occurs as soon as all new content
> has been downloaded from the server. In particular, it happens before any
> conflict resolution has taken place. On one hand, it seems useful to allow
> hooks to participate in conflict resolution. On the other hand, it comes as
> something of a surprise; I would have expected the "post-" hook to be run at
> the end of the process rather than in the middle.
> My application involves translating file formats between a
> version-controlled archive format and a derived format for deployment. I
> imagine this will be a fairly typical scenario. But given the current hooks,
> there's really no way to support this operation properly, since it needs to
> see a consistent set of post-integration files.
> I suggest adding another update hook. Rename the current post-update hook to
> pre-integrate or some variation of that, then redefine the post-update hook
> to run when the OK button on the update panel is clicked.
> The second issue is that there doesn't seem to be any triggering of hooks
> during a reversion or switch. Again, this is problematic because it thwarts
> efforts to keep derived data synchronized with version-controlled data. I am
> not so sure of the proper approach to this issue, though. In my case,
> triggering of the update hooks would solve the problem. But there may be
> reasonable scenarios in which the client-side software wants to distinguish
> between the various cases.
I've added an issue with your requests:
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-06-21 18:30:54 CEST