| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: branches_of_interest.txt |
| Date: | 2018-07-02 12:33:42 |
| Message-ID: | CA+TgmoYZ4ePwu04Ps3uLYO4FfEYZfDswcdPCBCmu7GXs53uMpg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 2, 2018 at 8:18 AM, Andrew Dunstan
<andrew(dot)dunstan(at)2ndquadrant(dot)com> 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 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 branches_of_interest.txt
> git commit -m 'initial content' branches_of_interest.txt
> git push origin HEAD
> git checkout master
>
> The new branch won't share any history or files with the existing branches.
Seems like too much magic to me.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ildus Kurbangaliev | 2018-07-02 12:56:24 | Re: [HACKERS] Custom compression methods |
| Previous Message | Robert Haas | 2018-07-02 12:32:45 | Re: Explain buffers wrong counter with parallel plans |