Subject: Re: [boost] Respecting a projects toolchain decisions
From: Nelson, Erik - 2 (erik.l.nelson_at_[hidden])
Date: 2010-12-27 10:39:25
Dean Michael Berris wrote on Monday, December 27, 2010
On Mon, Dec 27, 2010 at 1:27 PM, Vladimir Prus
>> Would you please specify a concrete example where innovation in a
>> library that you personally is contributing to is slowed down by
>> centralized version control?
>Boost.Pool is one, and the other was Boost.Iterators.
>With Boost.Pool, there's no maintainer around (that I know)
>who's checking patches submitted to it and making sure
>the changes make it into the releases.
>With Boost.Iterators, it took a while to get a patch for an
>additional iterator implementation to get into trunk -- and
>I'm not even sure if my patch has made it into the release yet.
It's not clear to me that these problems have anything to do with
Subversion... regardless of which vcs is used, *someone* is going to be
the designated maintainer/owner of the library, and if you can't get
them to include your patches, your patches won't be in the Boost
In that case you'd need to do the same thing you would do under the
current system... get yourself named maintainer/owner and then do it
Am I missing something there?
It seems to me that there's no shortage of innovation going on in
Boost... I've seen many fine libraries released over the years. My
observation is that there's some shortage of people who want to do the
laborious work... review manager, release manager, BoostCon organizer,
etc. My hat's off to the folks that do the heavy lifting there, and it
seems reasonable that they should have a larger voice on how that
This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited.
Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law.
The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses.
References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link:
http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk