[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v3 0/6] The remaining x86_64-gnu patches
|
From: |
Joseph Myers |
|
Subject: |
Re: [PATCH v3 0/6] The remaining x86_64-gnu patches |
|
Date: |
Tue, 2 May 2023 18:27:43 +0000 |
On Tue, 2 May 2023, Sergey Bugaev via Libc-alpha wrote:
> It would also probably make sense to mention my other changes, of
> which there have been many, in the NEWS (would a simple "many fixes
> and improvements in the Hurd port" suffice?)
That may well be an appropriate way to describe them (if you haven't
opened individual bug reports in Bugzilla; if a bug is reported in
Bugzilla, then marked FIXED after the commit with the target milestone set
to the first mainline release with the fix, it will automatically be
listed in the list of fixed bugs in NEWS).
> Am I supposed to write a patch for this, or will somebody else do it?
The general expectation is that someone adding a significant new feature
also does the NEWS update, and someone adding a new ABI does the
build-many-glibcs.py update.
> Will adding it to build-many-glibcs.py automatically enable some sort
> of server-side CI for this configuration?
My build-many-glibcs.py bots automatically run the compilation parts of
the testsuite for all configurations included in that script.
--
Joseph S. Myers
joseph@codesourcery.com