From: Sergey Bugaev <bugaevc@gmail.com>
To: Joseph Myers <joseph@codesourcery.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 17:16:38 +0300 [thread overview]
Message-ID: <CAN9u=Hd8_Ei-c6ojCNgfsDc-=uywiLFR_DyZoDBFpmb5g74sPA@mail.gmail.com> (raw)
In-Reply-To: <356bd2f-fe5f-aea1-4593-34e3b1287fa9@codesourcery.com>
Hello,
On Tue, May 2, 2023 at 5:03 PM Joseph Myers <joseph@codesourcery.com> wrote:
> On Sat, 29 Apr 2023, Sergey Bugaev via Libc-alpha wrote:
>
> > If these patches are pushed, it should be possible for anyone to build
> > x86_64-gnu glibc just out of Git master, without having to dig through
> > the mailing list archive for uncommited patches.
>
> In that case I think there should be a patch to build-many-glibcs.py to
> add an x86_64-gnu configuration, as well as updates to NEWS and README to
> reflect the new support for such a configuration.
yes, that would be great!
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?)
Am I supposed to write a patch for this, or will somebody else do it?
Will adding it to build-many-glibcs.py automatically enable some sort
of server-side CI for this configuration?
Sergey
next prev parent reply other threads:[~2023-05-02 14:16 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 [this message]
2023-05-02 18:27 ` Joseph Myers
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='CAN9u=Hd8_Ei-c6ojCNgfsDc-=uywiLFR_DyZoDBFpmb5g74sPA@mail.gmail.com' \
--to=bugaevc@gmail.com \
--cc=bug-hurd@gnu.org \
--cc=joseph@codesourcery.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).