OK, will fork, patch, and pull request as described in the github material. Still assessing the impact, namely if the same fault applies to other client/api areas.
------------------------------------------------------------------------------------------------------ Jason Richard Groothuis bSc(compSci) ------------------------------------------------------------------------------------------------------ > Subject: RE: [boinc_dev] Procedure for making a correction > Date: Tue, 3 Mar 2015 22:00:14 -0500 > From: [email protected] > To: [email protected]; [email protected] > > The easiest right now would be to submit a pull request on github. > > https://github.com/BOINC/boinc > > ----- Rom > > -----Original Message----- > From: boinc_dev [mailto:[email protected]] On Behalf Of > Jason Groothuis > Sent: Tuesday, March 03, 2015 9:23 PM > To: [email protected] > Subject: [boinc_dev] Procedure for making a correction > > Hi All, I am currently examining a small resource leak (long standing) > with respect to Boincapi on Windows, with Static C-Runtime linkage. > What is the preferred mechanism for patch & supporting information > submission ? Just post supporting information and a .patch / .diff here > ? > > ------------------------------------------------------------------------ > ------------------------------ > Jason Richard Groothuis > bSc(compSci) > > ------------------------------------------------------------------------ > ------------------------------ > > _______________________________________________ > boinc_dev mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
