WC-NG: Switching between base and working

[Bert Huijben <rh...@sharpsvn.net>]

Hi,

Working on the property switch code I found the following cases where we
switch entries from working to base or vice versa:
(And instead of keeping them in a private archive I just post them here)

Base->working
* adm_ops.c: mark_tree_copied()
* adm_ops.c: svn_wc_add4 (when adding files as copied)
* update_editor.c: set_copied_callback
* update_editor.c: schedule_existing_item_for_re_add

The adm_ops code is indirectly called from copy.c, which does more entry
mangling that will never work on a central database. (Just copying all files
below a path.. then run cleanup.. and then fixing the wc.db via entries
handling in adm_ops.c)

Working->base
* update_editor.c: close_file()
* update_editor.c: close_directory()
This is triggered by switching/updating locally added files/directories.

The post commit logic is already based on wc_ng primitives and I don't see
failures on testing properties there after r40319.

All these places will need wc_ng specific handling to keep new status data.
(Checksums, properties, etc.). I'm working on a patch that makes properties
survive these steps, but pristine file handling will need similar handling
if we don't rewrite these cases to wc_db based code first.

	Bert

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2413285