https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121373
--- Comment #4 from printfne at gmail dot com --- (In reply to Andrew Pinski from comment #3) > (In reply to printfne from comment #2) > > (In reply to Andrew Pinski from comment #1) > > > > For some reasons, I couldn't find this patch in the short term. > > > > > > Found it: > > > > > > https://inbox.sourceware.org/gcc-patches/ > > > caltx_hphw8x+rysuqlmpgz7s3qbfrmuzs5xtr6v8tbtgeqq...@mail.gmail.com/T/#u > > > > > > https://patchwork.sourceware.org/project/gcc/patch/ > > > caltx_hphw8x+rysuqlmpgz7s3qbfrmuzs5xtr6v8tbtgeqq...@mail.gmail.com/ > > > > > > > > > I noticed you didn't CC libstd...@gcc.gnu.org on the patch. > > > > First of all, I would like to thank you for your reply. After reading it, I > > still have some confusion. > > > > Yes, both of these emails were sent by me. The first time I sent them, I > > didn't CC the maintainer. So, after waiting for a week, I CCed the > > maintainer and resent them. > > As far as resending a patch after a week, usually we wait 2 weeks before > pinging patches, this is documented at > https://gcc.gnu.org/contribute.html#patches: > Pinging patches, Getting patches applied > If you do not receive a response to a patch that you have submitted within > two weeks or so, it may be a good idea to chase it by sending a follow-up > e-mail to the same list(s). Patches can occasionally fall through the > cracks. Please be sure to include a brief summary of the patch and the URL > of the entry in the mailing list archive of the original submission. > > > > Do I need to CC both the maintainer and > > libstd...@gcc.gnu.org at the same time? > > So for libstdc++ patches, they should be sent to gcc-patches@ and > libstdc++@. This is partly documented on > https://gcc.gnu.org/contribute.html#patches : > > When you have all these pieces, bundle them up in a mail message and send it > to the appropriate mailing list(s). (Patches will go to one or more lists > depending on what you are changing.) For further information on our source > repository, see the Anonymous read-only Git access and Read-write Git access > pages. > > > > > > As for not finding the patch, does it mean that I need to attach an > > attachment in the email? Or can it be done like in these two emails? > > > > > Also, > > regarding the issue of the signatory, is this one generated by GitHub, or do > > I have to change it to my own email? > > For the signed-off-by, it should be your own email address as it is for DCO > which you can read up via https://gcc.gnu.org/contribute.html#legal . Thank you for your patient guidance. It has greatly benefited me. I will read the links and the instructions you provided, and then write the email again. Thank you very much.
