Upstreaming the glibc Hurd port
Joseph Myers
joseph@codesourcery.com
Thu Jan 18 15:35:00 GMT 2018
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 - it allows glibc people to look over them and point out coding
standards issues to be addressed globally by people less familiar with the
conventions used in glibc. (Though when those issues are addressed the
fixes should be integrated into each patch as part of a rebase, rather
than simply adding another patch to the branch that fixes coding standards
issues with the previous patches.)
(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.)
--
Joseph S. Myers
joseph@codesourcery.com
More information about the Libc-alpha
mailing list