Re: Rejecting commits to a 1.5 server from clients < 1.5

On Oct 24, 2007, at 9:31 PM, Lars Gullik Bjønnes wrote:

> This is probably something I have not understood clearly yet: with a
> 1.5 client will mergeinfo always be sent, even if you run without
> '-g'?
>
> If not, is it enough to enforce 1.5 client? Must I not also be able to
> enforce '-g'?

(Note that, in the current state of trunk/, things have been
reversed: there's no "-g" at all for merge, but rather you have to
specify "--ignore-ancestry" to turn "-g-like" behavior off. But your
question remains, of course.)

No, we don't have to militate that all users user the merge info.
The option is there for 1.5 clients.

You might wonder why we're so up-in-arms about preventing 1.4 clients
from leaving this info out, if we're willing to let 1.5 clients do it
by choice. The answer is that they do have the choice, and if they
take it, then they're accepting responsibility for the consequences.

-==-
Jack Repenning
Chief Technology Officer
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
office: +1 650.228.2562
mobile: +1 408.835.8090
raindance: +1 877.326.2337, x844.7461
aim: jackrepenning
skype: jrepenning

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 25 06:28:11 2007