Re: Supporting multiple WC formats

2017-09-14 Thread Branko Čibej
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

Re: Supporting multiple WC formats

2017-09-14 Thread Branko Čibej
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

Re: Supporting multiple WC formats

2017-09-14 Thread Branko Čibej
On 14.09.2017 14:46, C. Michael Pilato wrote: > On 09/14/2017 12:01 AM, Branko Čibej wrote: >> As you may have noticed, I started implementing support for multiple WC >> formats on the better-pristines branch, as a prelude to adding support >> for compressed pristines without forcing users to

Re: Supporting multiple WC formats

2017-09-14 Thread C. Michael Pilato
On 09/14/2017 12:01 AM, Branko Čibej wrote: > As you may have noticed, I started implementing support for multiple WC > formats on the better-pristines branch, as a prelude to adding support > for compressed pristines without forcing users to upgrade all their > working copies. Sweet! > The

Re: Supporting multiple WC formats

2017-09-14 Thread Johan Corveleyn
On Thu, Sep 14, 2017 at 6:01 AM, Branko Čibej wrote: > As you may have noticed, I started implementing support for multiple WC > formats on the better-pristines branch, as a prelude to adding support > for compressed pristines without forcing users to upgrade all their > working

Supporting multiple WC formats

2017-09-13 Thread Branko Čibej
As you may have noticed, I started implementing support for multiple WC formats on the better-pristines branch, as a prelude to adding support for compressed pristines without forcing users to upgrade all their working copies. There's an overview in the branch readme file, but the basic idea is