RE: svn commit: r1030912 - in /subversion/trunk/subversion/libsvn_wc: adm_crawler.c update_editor.c
From: Bert Huijben <bert_at_qqmail.nl>
Date: Thu, 4 Nov 2010 14:07:44 +0100
> -----Original Message-----
Some time ago I hinted about creating a special wc-ng status for 'pinned' nodes.
This would introduce a well defined foundation in wc-ng that we can use for both file-externals (now) and viewspecs (later).
The simple definition for 'pinned' I had was: only valid on BASE (op_depth 0) nodes and handled as status 'normal'. The only exception to handling as normal would be that the adm crawler reports these nodes as excluded (like this patch does) so a second step could update them (from a different path, revision and/or repository).
The current file externals implementation still lacks documentation and a proper design and I'm -0 to -1 on extending file externals support (like that in this commit) without creating a proper design for file externals first.
The pinned status would make it very cheap to check for these relatively uncommon special nodes in a working copy, while adding a check for file-externals adds an extra database query to the most common code path in the update editor.
This is an archived mail posted to the Subversion Dev mailing list.