This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hi, Yeah I did send the patch to the gcc-patches mailing list, link: https://gcc.gnu.org/ml/gcc-patches/2017-03/msg00352.html But I missed sending changeLog. I hope the patch is fine now, updating the changeLog content as per your instruction and attaching, please find. I thought first I need approval from the community for the patch, and then do I need to submit/commit it anywhere ? Can you please guide me through the submission process ? Do I need to send this changeLog to gcc-patches as well ? Thanks and Regards, Nitish On Tue, Mar 21, 2017 at 1:25 AM, Joel Brobecker <brobecker@adacore.com> wrote: >> This defect is marked for GDB-8.0 branching. >> I have sent the patches earlier and got some review comments, changed >> the patch accordingly and sent again, but didn't get any feedback. >> I have uploaded the patch to the defect 21187 as well on bugzilla. >> Defect: https://sourceware.org/bugzilla/show_bug.cgi?id=21187 >> Consider this mail as reminder and I am attaching the proposed patch once again. > > Where did you send the patches? I thought you'd have sent them to > gcc-patches, but I couldn't find it in the gcc-patches mailing-list > archives... > >> 2016-03-01 Nitish K Mishra <nitismis@in.ibm.com> >> >> * configure.ac: Include one more option "--disable-staticlib" >> to link libstdc++ and libgcc dynamically. > > Your ChangeLog will need to include the following piece of info: > > * configure: Regenerate. > > Can you send us an update on the patch submission process? > > Thank you, > -- > Joel
Attachment:
ChangeLog.txt
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |