On 10/4/07, Erik Huelsmann <ehuels@gmail.com> wrote:
> > > There are lots of people stuck using old clients. For example, a user
> > > might be forced to use an old version of a development tool, and then
> > > forced to use an old SVN integration in that development tool. They
> > > also install the latest TortoiseSVN, and the next thing they know they
> > > cannot read any of their WC's with their old development tool. This
> > > is a big problem and will hit way more people than the scenario above.
> >
> > This is a compelling argument, though. Ouch.
> >
> > I guess I'd feel better if there were some screaming warning that
> > happened before an auto-format-bump happened. "WARNING: this is an
> > svn 1.5 client, and it's about to render your working copy unusable by
> > older versions. Are you should you want to proceed?" If the svn
> > commandline client, TSVN, and Subclipse all agreed to flash this
> > warning, I think we'd have 95% of the client base covered.
>
> We could choose to bump the format only when people use depths other
> than infinity (and new working copies)? That would affect only the
> group actually using depths. (Which actually *should* be affected,
> because this fix is for them...)
Yes, that was exactly my thought. If this is the situation that
creates the "problem" then lets defer the bump until it happens. Then
it is at least reasonable and understandable to the user and they can
likely avoid it as necessary.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 4 16:48:51 2007