On Mon, Jul 2, 2018 at 8:18 AM, Andrew Dunstan
<andrew.dunstan@2ndquadrant.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
