Re: Upstreaming the glibc Hurd port

[Samuel Thibault <samuel.thibault@gnu.org>]

Joseph Myers, on jeu. 18 janv. 2018 15:34:56 +0000, wrote:
> On Thu, 18 Jan 2018, Samuel Thibault wrote:
> > Coding standards can be worked on by anybody, this is really something
> > that bug-hurd people can unload us from.
> 
> Which is also something that having a branch with the patches is helpful 
> for -

Well, we already have that on

git clone git.savannah.gnu.org:/srv/git/hurd/glibc.git/

with almost a hundred branches to be looked after...
Not all of them are necessary for managing to build glibc. Some of them
are just hacking, others are perhaps almost ready to commit, just
missing changelogs & formatting. That's the triaging thing that takes
time, and having to do all the work including changelogs & formatting
makes it get lower in my global TODOlist.

That repo is not on top of master, but on top of the oldest glibc used
by the few GNU/Hurd distros. That's currently 2.24, but we have branches
to fast-forward that to 2.25 and 2.26.

> (A branch close to current master also provides a basis for anyone working 
> on build-many-glibcs.py support for Hurd, if you don't already have such 
> support among your glibc patches.)

That's why I suggested just committing the required patches to a branch
that we rebase regularly, so there's a master that does build.

Samuel