On Mon, Aug 31, 2026 at 9:31 AM Jonathan Yong <[email protected]> wrote:
>
> On 8/30/26 17:31, Zhongteng Gui wrote:
> > On 2026/08/31 01:16, Jonathan Yong wrote:
> >> On 8/30/26 15:33, Zhongteng Gui wrote:
> >>> On 2026/08/19 16:15, Richard Biener wrote:
> >>>> On Tue, Aug 18, 2026 at 5:31 PM LIU Hao <[email protected]> wrote:
> >>>>>
> >>>>> 在 2026-8-17 16:54, Richard Biener via Gcc 写道:
> >>>>>> Maintainers of the respective ports should propose such changes, then 
> >>>>>> they can
> >>>>>> easily be accepted.
> >>>>>
> >>>>> There was a discussion back in March, but no further action was taken:
> >>>>> https://gcc.gnu.org/pipermail/gcc/2026-March/247820.html
> >>>>
> >>>> I'd like to see separate proposals for each individual change, proposed
> >>>> in patch form to gcc-17/criteria.html, ideally from respective target/OS
> >>>> maintainers, but at least acked by them.
> >>>>
> >>>> The web pages are in git as well, git://gcc.gnu.org/git/gcc-wwwdocs.git
> >>>>
> >>>> Sorry if that wasn't clear.  Approval would be from release managers.
> >>>>
> >>>> Thanks,
> >>>> Richard.
> >>>>
> >>>>> (By the way, GCC 17 is missing from https://gcc.gnu.org/releases.html.)
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Best regards,
> >>>>> LIU Hao
> >>>
> >>> Cc Jonathan Yong. Seemes like you're the only maintainer of Cygwin and 
> >>> MinGW-w64.
> >>
> >> I already replied and agreed to drop 32-bit cygwin for 64-bit cygwin and
> >> changing i686-mingw32 to i686-w64-mingw32 and adding x86_64-w64-mingw32.
> >>
> >> Am I missing something?
> >>
> >
> > Sorry, I didn't notice that LH already sent 2 patches to gcc-patches list 
> > and
> > you've replied. But looks like the 2 patches haven't been commited?
>
> Richard, are maintainers supposed to push to gcc-wwwdocs?

Yes, approved patches can be pushed by anybody with access.

Richard.

>

Reply via email to