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

Re: Is it a bug or by design?

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Thu, 06 May 2010 19:14:36 +0200

On 06.05.2010 13:30, Serge Tumanyan wrote:
> Hello, Simon.
>>> I has tryed to use TSVN client hooks and ran into a trouble:
>>> I have added a post update hook and assumed that this one should work
>>> after
>>> the checkout, switch and update commands but found out that it works only
>>> after the update command. Is this by design or it is a bug? If this by
>>> design - can the hooks for checkout and switch commands be added to TSVN?
>>> It
>>> reduces productivity when you can not recompile the WC after the checkout
>>> in
>>> one step or after switching branches immediately and need to start a
>>> false
>>> update process to start a script. The missing hooks for the switch
>>> command
>>> tortures me especially much because I usually use switch command really
>>> often for my development tasks.
>> Why checkout? The hook scripts have to be set up for a specific WC, so
>> if you have not checked out a WC yet the hook does not exist.
> I am checking out the WC and using post update hook - that means that WC
> should already exist, shouldn't it?
>> I think a switch operation could just use the corresponding update
>> hooks because update is really just a special case of switch with no
>> path change.
> Right now it doesn't and this fact is rather unpleasant to me.

Can you file an issue for this please?
Just add a feature request that the hook script(s) should also get
invoked for switch/checkout.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-05-06 19:14:42 CEST

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