Hi, Thanks to the goodwill of the GCC maintainer, my name was included in the commit log. I would like to take this opportunity to study more and contribute to free and very important software such as GCC. https://github.com/gcc-mirror/gcc/commit/16d752a514033a9e37fed2a7f78024e222ca26b9
Best Regards, Takahashi Akari GPG Key: 9DD8 F529 83A0 3182 D318 6184 9309 E8D2 2FD4 4365 On Sat, Sep 10, 2022 at 2:00 AM Mark Wielaard <m...@klomp.org> wrote: > > Hi, > > On Sat, Sep 10, 2022 at 12:53:26AM +0900, Akari Takahashi via Gcc wrote: > > I read the linked message exchange carefully. After that, I tried to git > > clone the Git repository following the steps in the link below, but I get a > > permission error message. What are the next steps? > > https://gcc.gnu.org/gitwrite.html#setup > > > > I posted to the following mailing list before this application. > > https://gcc.gnu.org/pipermail/gcc-patches/2022-September/601320.html > > Your patch is unnecessary, the brackets are added by the > MEM_SIZE_KNOWN_P define. You don't need git write access. If you post > a proper patch someone will review it and commit it for you. This is > an offtopic request in this email thread. Please stop trying to get > git write access by writing to various mailing lists, if you need it > someone will tell you and point you to the proper process to follow. > > Thanks, > > Mark
