Karl Fogel wrote:
> Branko Čibej <brane_at_xbc.nu> writes:
>
>> Because then every client that wants to be comparable to others has to
>> implement that. Even those that don't or can't use the working copy
>> library; such as, for example, the dav-autocommit "client". Doing this
>> on the server side (with a kind of hardlink equivalent) would be
>> completely transparent to all clients.
>>
>> Sure, that would change the server-side revision from a tree to a DAG;
>> but no-one except the server would notice that.
>>
>
> Hmmm. A general comment:
>
> Brane, I sometimes get the feeling that your design thoughts are based
> on use cases that may not be obvious to others -- that you're thinking
> of ways of using Subversion that you haven't articulated. If you're
> waiting for people to ask, don't :-). Much better to just spell out the
> use case up front.
>
"CVS Modules done right"
"Unix (directory) hard links"
"Server-side view configurations" for someone used to ClearCase terminology
One other advantage of this being server-side is that the client doesn't
have to grow yet another command-line option to control which view
configuration it wants to use, which makes it all easier to explain.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-04-25 13:52:15 CEST