On 2023-01-13 Fr 19:33, Justin Pryzby wrote:
> On Fri, Jan 13, 2023 at 05:20:41PM -0500, Andrew Dunstan wrote:
>> Over at [1] there was some discussion of moving knowledge of what's
>> required to be fixed from old branch repos to be able to upgrade them
>> into the core code, instead of having i
On 2023-01-13 Fr 19:49, Tom Lane wrote:
> Andrew Dunstan writes:
>> Here's a piece of WIP for that, in the form of a perl module that
>> provides a function that takes an old version number / tag and provides
>> the set of sql statements that need to be run to make the old repo
>> upgradeable. I
Andrew Dunstan writes:
> Here's a piece of WIP for that, in the form of a perl module that
> provides a function that takes an old version number / tag and provides
> the set of sql statements that need to be run to make the old repo
> upgradeable. It still needs a good deal of polish, but it's a
On Fri, Jan 13, 2023 at 05:20:41PM -0500, Andrew Dunstan wrote:
> Over at [1] there was some discussion of moving knowledge of what's
> required to be fixed from old branch repos to be able to upgrade them
> into the core code, instead of having it reside in a buildfarm client
> module.
Is this in
Over at [1] there was some discussion of moving knowledge of what's
required to be fixed from old branch repos to be able to upgrade them
into the core code, instead of having it reside in a buildfarm client
module.
Here's a piece of WIP for that, in the form of a perl module that
provides a funct
