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
On Tue, 2 May 2023, Samuel Thibault via Libc-alpha wrote:
> Joseph Myers, le mar. 02 mai 2023 14:03:16 +, a ecrit:
> > 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 G
Joseph Myers, le mar. 02 mai 2023 14:03:16 +, a ecrit:
> 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
Hello,
On Tue, May 2, 2023 at 5:03 PM Joseph Myers 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
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 patc
These are the patches that I have locally that have not (yet) been
pushed. Most of them I have already sent previously, but have made
changes to since then. Please see the notes on individual patches.
I'm putting "v3" on the whole series because some of the patches here
have already been through v