On 2/9/2017 6:59 AM, Groke, Paul via Boost wrote:
Hi,
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of John Maddock Sent: Mittwoch, 8. Februar 2017 19:05
For the config stuff, either create a PR or just email me direct. The other 2 libraries are maintained so PR's or bug reports should get dealt with.
Can I generally create PRs on GitHub for all Boost libraries, or are some parts still maintained/developed somewhere else?
Everything is on Github.
And should I create three distinct PRs, one for the configure script change, one for the configure tests and one for the compiler/library/platform headers? Or just a single "one with everything" PR? I think three distinct PRs might be better but I also wouldn't mind putting everything in the same request.
When you create a PR for a library you should include all changes you want to make for it in the single PR. There is no need to create multiple PRs since you have already forked the library in order to potentially create your PR. If you need to change multiple libraries, then you will have separate PRs for each library. However if they need to be co-ordinated for all changes to work you need to say so when the PRs are created.
Also I have to wait for approval from my company, so it might be some days before I can start.
Understood.
Cheers, Paul
Ps: Please excuse the footer. I've already asked IT if I can suppress that somehow but not yet received an answer...
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. Dynatrace Austria GmbH (registration number FN 91482h) is a company registered in Linz whose registered office is at 4040 Linz, Austria, Freistaedterstrasse 313