[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230403154435.GH3630668@port70.net>
Date: Mon, 3 Apr 2023 17:44:35 +0200
From: Szabolcs Nagy <nsz@...t70.net>
To: Rich Felker <dalias@...c.org>
Cc: 王洪亮 <wanghongliang@...ngson.cn>,
musl@...ts.openwall.com
Subject: Re: add loongarch64 port v6.
* Rich Felker <dalias@...c.org> [2023-04-03 10:42:49 -0400]:
> On Mon, Apr 03, 2023 at 03:35:23PM +0200, Szabolcs Nagy wrote:
> > * 王洪亮 <wanghongliang@...ngson.cn> [2023-03-17 16:41:26 +0800]:
> > > Hi, Rich
> > >
> > > Do I need to do any other work with this patch v6？
> >
> > where is v6?
> >
> > i only see v5 patch on the list
>
> The v6 was just sent as a link to git repo, I think. And indeed now I
> need to make sure I can find the copy I grabbed to look at last time,
> or else look over it again to ensure this is still correct and still
> what I reviewed. This is why patches should always be sent as
> attachments (thus immutable) not links.
>
> I'm trying to wrap up the release now and expect I will apply this
> (with the minor formatting fixes I promised I could make myself at
> merge time) right after release.
i was asking because of this glibc patch:
https://sourceware.org/pipermail/libc-alpha/2023-April/146897.html
i dont understand that change (loongarch is in glibc since 2.36 release).
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
