This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Fw: Re: [RESEND] [PATCH] PPC64: First in the series of patches implementing
- From: David Edelsohn <dje dot gcc at gmail dot com>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: GT <tnggil at protonmail dot com>, "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>, Tulio Magno Quites Machado Filho <tuliom at linux dot ibm dot com>, Jeffrey Scheel <scheel at us dot ibm dot com>
- Date: Thu, 7 Mar 2019 14:27:59 -0500
- Subject: Re: Fw: Re: [RESEND] [PATCH] PPC64: First in the series of patches implementing
- References: <CAGWvnykktWuDVLrMrOiLrGV9aOUUQNd8Bf1FiiWbQ_G-aXJyvQ@mail.gmail.com> <Va5DLyFouG-pOYSW0osnuTg2RRjCEsQF6mYXCKNTFZSE4h0fX0kAOkH8-0EMivO0tMrSn-T2jK7GBNBcQnI_vjkMjgeb7sjPscHVOlqf_ao=@protonmail.com> <alpine.DEB.2.21.1903012207200.29803@digraph.polyomino.org.uk> <pY1zcuIUDeySpFynMv979KQmb37qfZnrcQ98ldKaG5znsTC5i2CocB1NC_YdIV3SDxRr4x8AAYTL2bih3rlKv6wP7V1wLSHawwZRc1KCLHw=@protonmail.com> <alpine.DEB.2.21.1903012354330.29803@digraph.polyomino.org.uk> <_tezejCH0vYrGXfP1IeMTR6g0HK034WMZfvem-g9O-_OzFYr6LnkLIIVQCooAxxGQOEt21ffWRRhngLBZO8qqrTkvVTck4YoDnUcQEmfxy4=@protonmail.com> <CAGWvny=7zgsoi56YmyP8-_8xkhw_-KMm+g8JuDyL-hEyHVxTvg@mail.gmail.com> <N6kmy1CnEKz5wrqCSs1fTdqLzepvHZWHRcflz_5lYeS07m0HbvF4WblUXQbUGDh0vgjOvLjlrcIJcJ9X5QoQX_kN6rQ4bhQ5xBwgDZUhI7A=@protonmail.com> <CAGWvnynLSR=-aK7eiWGgxVm6F_nLVjxq0c37m9M-GeMDOgeTNw@mail.gmail.com> <8TDbu1oDirvQTYg3dCpW6ovpZQUe7bU02QCGDkQ-CJ6bcMhr8fn_du7EGZIDM8JPp8dl5Mmd3WxF327Wh1xqVG35GmXnlHErAN1GMxQS4DQ=@protonmail.com> <alpine.DEB.2.21.1903071855480.16241@digraph.polyomino.org.uk>
On Thu, Mar 7, 2019 at 1:57 PM Joseph Myers <joseph@codesourcery.com> wrote:
>
> On Wed, 6 Mar 2019, GT wrote:
>
> > 2. There are repeated references to a branch that will be the home of the
> > patches until they can be merged into glibc master. What is the exact process
> > for creating the branch? Who is supposed to create it?
>
> You can create a branch on any git hosting site that is convenient for
> you.
>
> Processes for branches in the main glibc repository are described at
> <https://sourceware.org/glibc/wiki/GlibcGit>. Write access to the
> repository on sourceware is typically granted *after* someone has
> demonstrated experience working with the glibc community and producing
> good patches.
Joseph,
The patches are tied to a GLIBC BZ issue. The branch should be created
in the GLIBC repository by Tulio or someone, and then Bert's patches
pulled into the branch with the commit message tied to the BZ.
We have agreed that the patches should not be in Master and the
symbols not visible and exported until the ABI is defined. Bert
doesn't have control over the ABI, documentation, build infrastructure
nor GCC connection. That was not part of the issue requirement. He
needs to be allowed to contribute the work that reasonably is under
his control.
He doesn't need commit access himself. We need a branch where his
patches deemed acceptable will be placed until the rest of the
framework catches up.
Thanks, David