http://llvm.org/docs/DeveloperPolicy.html#making-and-submitting-a-patch discussing the rough way to approach this stuff.
Basically - a patch file attached to an email to cfe-commits with "patch" in the subject would be great. Patches should include changes to the test tree to verify the changes. - David On Tue, Mar 24, 2015 at 11:45 PM, jeaye <[email protected]> wrote: > On Mon, Mar 23, 2015 at 06:33:13PM +0800, jeaye wrote: > > Folks, > > > > I have been waiting for some time, from IRC pinging, to mailing list > > emailing, to bug tracker posting, for some changes to be > > reviewed/merged. There has been no activity. Someone suggested that I > > post here, so please consider bringing in these two fixes: > > > > 1) https://llvm.org/bugs/show_bug.cgi?id=22183 > > > > 2) https://llvm.org/bugs/show_bug.cgi?id=22184 > > > > Furthermore, there has also been no activity on my third issue (for > > which I don't have any commits) which is related: > > > > https://llvm.org/bugs/show_bug.cgi?id=22185 > > > > I have been waiting to release my project: > > https://github.com/jeaye/color_coded due to issues in libclang. Getting > > these two merged in would be a great step. > > > > Cheers, > > Jeaye > > Sending this back in with a PATCH in the subject, as it seems that's the > general practice. I have two patches that I'd like to get merged as soon as > possible; if there's yet another place I need to ask, please let me know. > _______________________________________________ > cfe-commits mailing list > [email protected] > http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits >
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
