[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: r21207 (Renaming --no-svndiff1 to --pre-1.4-compatible)

From: Malcolm Rowe <malcolm-svn-dev_at_farside.org.uk>
Date: 2006-08-23 13:07:47 CEST

On Tue, Aug 22, 2006 at 11:20:39PM -0400, Garrett Rooney wrote:
> Oh please, you're dramatically overstating the importance of this
> change. The flag may be obscure, but its use case is also obscure,
> there's no reason we should be wasting anyone's time on it when the
> vast majority of users will never even need to know of its existence.

I've just voted +1 on this in STATUS, approving the change, but I've not
merged it yet in case there's anyone else who'd like to register an

This shouldn't be about the name of the command-line option so much -
which by itself is, I agree, bikesheddy and obscure - but about the API
we're exposing (both programmatically and scripted). Does asking for
a repository to be created that doesn't use svndiff1 mean simply that,
or does it mean 'I'd like a repository that works with pre-1.4 clients'?

Currently, they're the same thing, but we're not promising that anywhere.
Max's change to conditionally bump the repository version number currently
depends upon the latter definition, and while we have the freedom to
change _that_ implementation whenever we like (it's our code, and it's
only run at repository-creation time), the bigger question is whether
we want to provide a way for users to specify the latter behaviour in
a guaranteed manner.

And, I must admit, the older command-line option name did suck.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 23 13:08:24 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.