Andres Freund writes:
> On 2018-07-01 11:41:07 -0400, Tom Lane wrote:
>> I can see the value of people other than you being able to change it,
>> but keeping it in the core repo seems like a kluge not a proper solution.
> FWIW, I've a manually maintained version of this in the scripts I use to
>
On 2018-07-01 11:41:07 -0400, Tom Lane wrote:
> Andrew Dunstan writes:
> > This file on the buildfarm server is used to tell clients which branches
> > we'd like built. When a new stable branch is created it's added manually
> > to this file, and when one gets to EOL it's removed from the file.
Robert Haas writes:
> On Mon, Jul 2, 2018 at 8:18 AM, Andrew Dunstan
> wrote:
>> An alternative would be to create a special branch within the core
>> repo for such data, something like this (The first two lines are the
>> ones that are most important):
>> ...
>> The new branch won't share any hi
On Mon, Jul 2, 2018 at 8:33 AM, Robert Haas wrote:
> On Mon, Jul 2, 2018 at 8:18 AM, Andrew Dunstan
> wrote:
>> Ideally this would be done as part of creating the new branch. Since
>> the web site doesn't have the same set of committers, a second metdata
>> repo like this seems sensible.
>> An al
On Mon, Jul 2, 2018 at 8:18 AM, Andrew Dunstan
wrote:
> Ideally this would be done as part of creating the new branch. Since
> the web site doesn't have the same set of committers, a second metdata
> repo like this seems sensible.
> An alternative would be to create a special branch within the cor
On Mon, Jul 2, 2018 at 4:45 AM, Magnus Hagander wrote:
>
>
> On Mon, Jul 2, 2018 at 10:39 AM, Peter Eisentraut
> wrote:
>>
>> On 01.07.18 17:41, Tom Lane wrote:
>> > I can see the value of people other than you being able to change it,
>> > but keeping it in the core repo seems like a kluge not a
On Mon, Jul 2, 2018 at 4:39 AM, Peter Eisentraut
wrote:
> On 01.07.18 17:41, Tom Lane wrote:
>> I can see the value of people other than you being able to change it,
>> but keeping it in the core repo seems like a kluge not a proper solution.
>> In particular, once it'd been around for awhile so t
On Mon, Jul 2, 2018 at 10:39 AM, Peter Eisentraut <
peter.eisentr...@2ndquadrant.com> wrote:
> On 01.07.18 17:41, Tom Lane wrote:
> > I can see the value of people other than you being able to change it,
> > but keeping it in the core repo seems like a kluge not a proper solution.
> > In particula
On 01.07.18 17:41, Tom Lane wrote:
> I can see the value of people other than you being able to change it,
> but keeping it in the core repo seems like a kluge not a proper solution.
> In particular, once it'd been around for awhile so that the master copy
> had diverged from the back branches' cop
Andrew Dunstan writes:
> This file on the buildfarm server is used to tell clients which branches
> we'd like built. When a new stable branch is created it's added manually
> to this file, and when one gets to EOL it's removed from the file. This
> is a rather cumbersome process, and it occurre
10 matches
Mail list logo
