[Modularization] Range and Spirit dependencies
Hello, Boost 1.55 has been out for some weeks. I repeat my recommendation to remove the Boost.Algorithm dependency from Boost.Range and the Boost.Serialization dependency from Boost.Spirit. http://thread.gmane.org/gmane.comp.lib.boost.devel/251966/focus=252090 http://thread.gmane.org/gmane.comp.lib.boost.devel/251966/focus=251968 http://thread.gmane.org/gmane.comp.lib.boost.devel/252250/focus=252293 Thanks, Steve.
Stephen Kelly wrote:
Hello,
Boost 1.55 has been out for some weeks.
I repeat my recommendation to remove the Boost.Algorithm dependency from Boost.Range
Please go ahead and merge this: https://github.com/boostorg/range/pull/24 Thanks, Steve.
Stephen Kelly wrote:
Please go ahead and merge this:
Bump. It has been two weeks. Thanks, Steve.
On 9/24/2014 2:42 AM, Stephen Kelly wrote:
Stephen Kelly wrote:
Please go ahead and merge this:
Bump. It has been two weeks.
Who are you addressing this to?
Eric Niebler wrote:
On 9/24/2014 2:42 AM, Stephen Kelly wrote:
Stephen Kelly wrote:
Please go ahead and merge this:
Bump. It has been two weeks.
Who are you addressing this to?
Anyone who has the authority to review/merge it. I suppose that's you and Neil and I-don't-know-who-else. Neil merged that one today anyway, thanks! Steve.
On 9/25/2014 3:49 PM, Stephen Kelly wrote:
Eric Niebler wrote:
On 9/24/2014 2:42 AM, Stephen Kelly wrote:
Stephen Kelly wrote:
Please go ahead and merge this:
Bump. It has been two weeks.
Who are you addressing this to?
Anyone who has the authority to review/merge it. I suppose that's you and Neil and I-don't-know-who-else.
You'll get better results by abiding by our posting guidelines.[*] In particular:
Put the Library Name in the Subject Line
When your post is related to a particular Boost library, it's helpful to put the library name in square brackets at the beginning of the subject line, e.g.
Subject: [Regex] Why doesn't this pattern match?
The Boost developers' list is a high-volume mailing list, and most maintainers don't have time to read every message. A tag on the subject line will help ensure the right people see your post.
I find this works much better than shouting into the void. ;-) Also, The maintainers list is not secret. It is included with every Boost distribution: https://github.com/boostorg/boost/blob/master/libs/maintainers.txt Eric [*] http://www.boost.org/community/policy.html
Eric Niebler wrote:
You'll get better results by abiding by our posting guidelines.[*] In particular:
Put the Library Name in the Subject Line
I did this. If putting 'Range' in the text of the subject is 'wrong', and only putting '[range]' with square brackets is 'right', then you might choose to clarify this in the policy. Thanks, Steve.
On 27 September 2014 10:36, Stephen Kelly
Eric Niebler wrote:
You'll get better results by abiding by our posting guidelines.[*] In particular:
Put the Library Name in the Subject Line
I did this. If putting 'Range' in the text of the subject is 'wrong', and only putting '[range]' with square brackets is 'right', then you might choose to clarify this in the policy.
It is already clearly stated explicitly in the policy. Eric is absolutely correct that this would have helped to get me attention more quickly. I have email rules to pick out the [range] emails. The relevant section from the link that Eric posted is: <Quote> Put the Library Name in the Subject Line When your post is related to a particular Boost library, it's helpful to put the library name in square brackets at the beginning of the subject line, e.g. Subject: [Regex] Why doesn't this pattern match? The Boost developers' list is a high-volume mailing list, and most maintainers don't have time to read every message. A tag on the subject line will help ensure the right people see your post. </Quote>
Thanks,
Steve.
I certainly wish to deliver in a timely manner within the constraints of my other life activities, but in this instance can't see how this particular issue could be made more clear. Feel free to email me directly. I'm very grateful for the effort you have put in to the modularisation and especially for going to the effort of putting together a merge request that was so easy to apply. Thanks, Neil Groves
participants (3)
-
Eric Niebler -
Neil Groves -
Stephen Kelly