You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Götz Reyher <go...@hamburg.de> on 2009/02/22 16:57:38 UTC
Question on client / working copy compatibility - part 2
Hi all,
-- thanks a lot for clarifying my first question - there is
(currently) no public API call to be used in order to get information
about the compatibility of two clients. Nice idea to add it to
svnclient.h, though.
Now another question, which is somewhat related to this:
I'm assuming that 1.7 clients are (planned to be) able to work on
local metadata, which is compatible with the 1.6 format, as long as
this metadata has not been upgraded explicitly by a 1.7 client? In
other words, could I continue to operate on my local wc using 1.6 and
1.7 clients in parallel? I would maybe loose some of the new features
of 1.7 in this case, but after explicitly upgrading my wc to 1.7
client format, I would be able to use the features (if any). Is this
the correct idea?
Sincerely,
Goetz
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1209861
Re: Question on client / working copy compatibility - part 2
Posted by Joe Swatosh <jo...@gmail.com>.
On Mon, Feb 23, 2009 at 7:42 AM, Hyrum K. Wright
<hy...@mail.utexas.edu> wrote:
>
> On Feb 22, 2009, at 12:27 PM, Joe Swatosh wrote:
>
>> On Sun, Feb 22, 2009 at 10:09 AM, Daniel Shahaf <d....@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 <gs...@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
>
Thanks for explaining.
--
Joe
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1215493
Re: Question on client / working copy compatibility - part 2
Posted by "Hyrum K. Wright" <hy...@mail.utexas.edu>.
On Feb 22, 2009, at 12:27 PM, Joe Swatosh wrote:
> On Sun, Feb 22, 2009 at 10:09 AM, Daniel Shahaf <d.s@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 <gs...@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
Re: Question on client / working copy compatibility - part 2
Posted by Joe Swatosh <jo...@gmail.com>.
On Sun, Feb 22, 2009 at 10:09 AM, Daniel Shahaf <d....@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 <gs...@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?
--
Joe
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1210308
Re: Question on client / working copy compatibility - part 2
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
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 <gs...@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.
> >
> > Once 1.7 upgrades a working copy to format version 11, then the 1.6
> > clients (and earlier) will not be able to read them. In fact, pre-1.7
> > clients will not even recognize the working copies *as* working
> > copies.
> >
>
> 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.
> --
> Joe
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1210120
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1210223
Re: Question on client / working copy compatibility - part 2
Posted by Greg Stein <gs...@gmail.com>.
On Sun, Feb 22, 2009 at 18:42, Joe Swatosh <jo...@gmail.com> wrote:
> Hi Greg,
>
> On Sun, Feb 22, 2009 at 9:16 AM, Greg Stein <gs...@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.
>>
>> Once 1.7 upgrades a working copy to format version 11, then the 1.6
>> clients (and earlier) will not be able to read them. In fact, pre-1.7
>> clients will not even recognize the working copies *as* working
>> copies.
>>
>
> Will tools/client-side/change-svn-wc-format.py still work to downgrade
> accidental upgrades?
Only if somebody writes it.
And that is going to be one SERIOUS chunk of work, if somebody
attempts it. The two formats are drastically different. That script
has been able to take advantage of the fact that each iteration is
only slightly different. Not so with 1.7.
Cheers,
-g
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1210193
Re: Question on client / working copy compatibility - part 2
Posted by Joe Swatosh <jo...@gmail.com>.
Hi Greg,
On Sun, Feb 22, 2009 at 9:16 AM, Greg Stein <gs...@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.
>
> Once 1.7 upgrades a working copy to format version 11, then the 1.6
> clients (and earlier) will not be able to read them. In fact, pre-1.7
> clients will not even recognize the working copies *as* working
> copies.
>
Will tools/client-side/change-svn-wc-format.py still work to downgrade
accidental upgrades?
--
Joe
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1210120
Re: Question on client / working copy compatibility - part 2
Posted by Greg Stein <gs...@gmail.com>.
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.
Once 1.7 upgrades a working copy to format version 11, then the 1.6
clients (and earlier) will not be able to read them. In fact, pre-1.7
clients will not even recognize the working copies *as* working
copies.
Cheers,
-g
On Sun, Feb 22, 2009 at 17:57, Götz Reyher <go...@hamburg.de> wrote:
> Hi all,
>
> -- thanks a lot for clarifying my first question - there is
> (currently) no public API call to be used in order to get information
> about the compatibility of two clients. Nice idea to add it to
> svnclient.h, though.
>
> Now another question, which is somewhat related to this:
>
> I'm assuming that 1.7 clients are (planned to be) able to work on
> local metadata, which is compatible with the 1.6 format, as long as
> this metadata has not been upgraded explicitly by a 1.7 client? In
> other words, could I continue to operate on my local wc using 1.6 and
> 1.7 clients in parallel? I would maybe loose some of the new features
> of 1.7 in this case, but after explicitly upgrading my wc to 1.7
> client format, I would be able to use the features (if any). Is this
> the correct idea?
>
> Sincerely,
>
> Goetz
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1209861
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1209985