Brane, you wrote two very detailed mails answering my question, and
ordinarily would get more than this brief "Thank you!" for your
efforts. However, I'm busily packing for a cross-country move, so
this grateful acknowledgement is all I can do right now. There are
various responses -- just responses, not necessarily counterarguments
-- I would normally make, but they'll have to wait.
-Karl
Branko Čibej <brane@xbc.nu> writes:
> The second problem is semantics.
>
> It's not just about formally distinguishing between copies and branches.
> This goes deeper.
>
> I submit:
>
> * When you make a branch, you want all that merge-tracking machinery
> to kick in.
> * You want easy answers to questions like "what changed on this
> branch?" and "where did we branch from?" and so on.
> * When you make a copy, you may want to vaguely remember what you
> copied, but you don't want any merge tracking or history from
> beyond the point of copy.
> * The above is again different from a rename, which is abstractly
> almost like a copy and delete, except that you /do/ want all
> history ... the changes in the name of the object are
> coincidental. (Note how filesystems treat "move" and "copy" quite
> differently in terms of inode identity, ownership and access rights.)
>
> All of these are superficially UI issues, and we even support them in a
> way (remember --stop-on-copy?), but really more as afterthoughts. And we
> don't support tag semantics at all.
>
> -- Brane
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 17 09:46:00 2007