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

Re: Question on client / working copy compatibility - part 2

From: Hyrum K. Wright <hyrum_wright_at_mail.utexas.edu>
Date: Mon, 23 Feb 2009 09:42:09 -0600

On Feb 22, 2009, at 12:27 PM, Joe Swatosh wrote:

> On Sun, Feb 22, 2009 at 10:09 AM, Daniel Shahaf <d.s_at_daniel.shahaf.name
> > wrote:
>> Joe Swatosh wrote on Sun, 22 Feb 2009 at 09:42 -0800:
>>> Hi Greg,
>>>
>>> On Sun, Feb 22, 2009 at 9:16 AM, Greg Stein <gstein_at_gmail.com>
>>> wrote:
>>>> svn 1.7 will *not* be able to write metadata within a 1.6 working
>>>> copy
>>>> (format version 10).
>>>>
>>>> svn 1.7 *may* be able to read a 1.6 working copy without upgrading.
>>>>
>
>>> Will tools/client-side/change-svn-wc-format.py still work to
>>> downgrade
>>> accidental upgrades?
>>>
>>
>> Note that 1.7 will *not* automatically upgrade the format of every
>> wc it
>> touches.
>>
>
> I figured it would be big to make that script work.
>
> It is probably that it not that important that it be supported if
> the 1.7
> upgrade is not automatic. But how does that play with Greg's
> statements above that 1.7 won't be able to write 1.6 metadata
> and only may be able to read it?

1.7 will be able to read enough to say "hey, this is an old working
copy, run 'svn cleanup' to upgrade it" and then do the upgrade when
requested. 1.7 will know enough to be able to run old logs and write
the results before upgrading. Other than that, 1.7 will only be able
to write 1.7 format working copies.

-Hyrum

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1215157
Received on 2009-02-23 16:42:30 CET

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.