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
git rm --cached -r .
>> wget https://buildfarm.postgresql.org/branches_of_interest.txt
>> git add branches_of_interest.txt
>> git commit -m 'initial content' branches_of_interest.txt
>> git push origin HEAD
>> git checkout master
>>
>> The new
branch within the core
> repo for such data, something like this (The first two lines are the
> ones that are most important):
>
> git checkout --orphan metadata
> git rm --cached -r .
> wget https://buildfarm.postgresql.org/branches_of_interest.txt
> git add branch
bout which one
> is more convenient to use.
>
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
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
a repo
kept up to date fairly continuously (every 5 minutes).Essentially what
we'd need is a script on the server called from cron which would do
something along the lines of
GIT_DIR=/path/to/local/clone git show
master:path/to/branches_of_interest.txt > htdocs/branches_of_inte
11 matches
Mail list logo
