Fw: Re: [RESEND] [PATCH] PPC64: First in the series of patches implementing

[GT <tnggil at protonmail dot com>]

> > > > 2.  A description on how to enable the code in order to test it without compiler
> > > >     support. A public branch/repository is ideal.
> > > >
> > >
> > > Sure, a branch is appropriate; the issues with lack of compiler support
> > > are issues for having the support on master. Then, maybe a wiki page that
> > > points to the glibc branch, the GCC branch (once available), the current
> > > work on the ABI, etc., so people can find all the relevant pieces.
> >
> > Agreed.
>
> 1.  So begin by cloning glibc to a new github project?
> 2.  Send patches for review to libc-alpha prior to pushing any new commit
>     onto the branch on github.
>
> 3.  When all reviewers accept changes in patch; rebase the working branch,
>     commit the changes and push to github.
>
>     Any changes needed to this workflow?
>

Found this: <https://sourceware.org/glibc/wiki/GlibcGit> which seems to be
how the public branch is to be created and maintained.

After reading through, my understanding is that a maintainer should create
the new branch and will be responsible for pushing accepted patches from
libc-alpha onto it.

Tulio, Joseph:

Of the handful who have commented thus far, only the two of you fit.
Would either of you take up the task?

Thanks.
Bert.