From: Joseph Myers <joseph@codesourcery.com>
To: Sergey Bugaev <bugaevc@gmail.com>
Cc: <libc-alpha@sourceware.org>, <bug-hurd@gnu.org>,
Samuel Thibault <samuel.thibault@gnu.org>
Subject: Re: [PATCH v3 0/6] The remaining x86_64-gnu patches
Date: Tue, 2 May 2023 18:27:43 +0000 [thread overview]
Message-ID: <b4e8c7db-b346-d23f-dfdf-ec6d1b446772@codesourcery.com> (raw)
In-Reply-To: <CAN9u=Hd8_Ei-c6ojCNgfsDc-=uywiLFR_DyZoDBFpmb5g74sPA@mail.gmail.com>
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
next prev parent reply other threads:[~2023-05-02 18:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-29 20:18 Sergey Bugaev
2023-04-29 20:18 ` [PATCH v3 1/6] hurd: Implement sigreturn for x86_64 Sergey Bugaev
2023-04-30 23:06 ` Samuel Thibault
2023-04-29 20:18 ` [PATCH v3 2/6] hurd: Implement longjmp " Sergey Bugaev
2023-04-30 23:16 ` Samuel Thibault
2023-04-29 20:18 ` [RFC PATCH v3 3/6] hurd: Replace reply port with a dead name on failed interruption Sergey Bugaev
2023-05-01 1:20 ` Samuel Thibault
2023-04-29 20:18 ` [PATCH v3 4/6] hurd: Add expected abilist files for x86_64 Sergey Bugaev
2023-04-30 23:18 ` Samuel Thibault
2023-05-01 10:20 ` Samuel Thibault
2023-05-01 17:33 ` Sergey Bugaev
2023-05-01 17:43 ` Samuel Thibault
2023-04-29 20:18 ` [RFC PATCH v3 5/6] hurd: Make it possible to call memcpy very early Sergey Bugaev
2023-04-30 23:21 ` Samuel Thibault
2023-04-29 20:18 ` [DO NOT PUSH PATCH v3 6/6] TMP hurd: Lower BRK_START Sergey Bugaev
2023-05-02 14:03 ` [PATCH v3 0/6] The remaining x86_64-gnu patches Joseph Myers
2023-05-02 14:16 ` Sergey Bugaev
2023-05-02 18:27 ` Joseph Myers [this message]
2023-05-02 15:17 ` Samuel Thibault
2023-05-02 18:24 ` Joseph Myers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4e8c7db-b346-d23f-dfdf-ec6d1b446772@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=bug-hurd@gnu.org \
--cc=bugaevc@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=samuel.thibault@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).