On 14.09.2017 17:03, Branko Čibej wrote: > On 14.09.2017 14:47, Branko Čibej wrote: >> On 14.09.2017 11:48, Johan Corveleyn wrote: >>> My opinion: don't allow upgrading individual externals-sub-wc's. It's >>> all or nothing IMHO. >> That's the way I'm leaning, too. I do have to figure out if the code for >> that is already in place, or whether I need some more wc-fu to invent it. :) > $ svn st > X foo > > Performing status on external item at 'foo': > svn: E155021: This client is too old to work with the working copy at > '/Users/brane/src/svn/test/bar/foo' (format 32). > You need to get a newer Subversion client. For more details, see > http://subversion.apache.org/faq.html#working-copy-format-change > > > The upgrade of the foo external working copy (using the client from the > better-pristines branch) worked without a hitch. So we currently do not > have any logic in the code to prevent partial upgrades or, in other > words, to prevent mixed-format working copies. > > This needs fixing ... preferably on trunk.
However ... didn't we have a published use case for upgrading very large working copies by upgrading subtrees first? Or was that just for upgrades from entries-based to wc.db-based working copies? -- Brane
