Delay creating the client/wc context until after we have finished
tweaking the config hash so that the full config is available when
creating the context.  In particular the SQLite exclusive locking
flag is available when first opening the wc_db.

* subversion/svn/svn.c
  (sub_main): Create context later.


git-svn-id: https://svn.apache.org/repos/asf/subversion/trunk@1447378 13f79535-47bb-0310-9956-ffa450edef68
Clear moved-here markers of nodes which were moved outside of a subtree
which is being deleted during an update.

Before this change, the move source node disappeared from the working
copy while the moved-here marker remained set at the destination, leaving
behind a dangling move.

Suggested by: philip

* subversion/libsvn_wc/wc-queries.sql
  (STMT_CLEAR_MOVED_HERE_RECURSIVE): New. Clears moved-here on a node and
   any moved-along children.

* subversion/libsvn_wc/wc_db.c
  (clear_moved_here): New helper function.
  (db_base_remove): When removing a conflicted node, clear moved-here markers
   at the destinations of moves which moved nodes outside the conflicted node.
   Add a FIXME comment explaining an alternative approach which we might want
   to implement in 1.9 and beyond.

* subversion/tests/libsvn_wc/op-depth-test.c
  (move_away_delete_update): This test now passes, so remove XFAIL marker.


git-svn-id: https://svn.apache.org/repos/asf/subversion/trunk@1447380 13f79535-47bb-0310-9956-ffa450edef68