RE: Transitioning from Rational Apex version control?

Daniel Berlin wrote:
> We were speaking about being able to do at some recent point on IRC.
> In particular, being able to auto-update to newer revisions of
> "unmodified on branch files".
>
> This is somewhat different than keeping a copy-history, because
> you just want to say "Use this revision for this file, from now on",
> since it unmodified. Unfortunately, even this requires schema changes
> to the repository schema (you need to add something to the nodes in
> a given revision to let them be shared with some other node, but have
> a different predecessor id), so it can't happen until 2.0.

Apologies if I just plain "don't get it" (I'm not familiar with
predecessor ids on nodes or anything that deep), but couldn't
this be implemented in the client side using only a property?

Here's my thinking:
The svn client, when it's about to attempt updating a file, checks
for the presence of a theoretical "svn:no-update" property;
if not present, the update continues as normal. Otherwise,
updating that particular node is skipped, and the batch
continues.

This would be a fairly flexible option, IMHO... and
should be fairly straightforward to implement.
(disclaimer: I've not actually tried hacking the
svn code so it may be more complex than I realise)

Any obvious flaws in my reasoning?

-- 
Robert Hunter
*****************************************************************************
This communication, including any attachments, is confidential.
If you are not the intended recipient, you should not read it
- please contact me immediately, destroy it, and do not copy
or use any part of this communication or disclose anything about it,
Thank you.
Please note that this communication does not designate an information system
for the purposes of the Electronic Transactions Act 2002
******************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org