Boost logo

Boost Users :

Subject: Re: [Boost-users] How to get bug reports addressed
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2011-01-07 15:06:28


AMDG

On 1/7/2011 10:03 AM, Geoffrey Romer wrote:
> One reasonable approximation to this approach would be if I could generate a
> patch file that takes one release version of Boost to the next; I could then
> apply that patch to perform the upgrade, and my local modifications would
> remain intact (except in the case of conflicts, which I can merge by hand).
> However, I haven't been able to work out how to identify a particular
> release version of Boost in the repository, in order to generate such a
> patch.

That's easy:

>svn ls http://svn.boost.org/svn/boost/tags/release
Boost_0_7_0/
Boost_0_7_2/
Boost_0_7_8/
Boost_0_7_9/
Boost_0_8_1/
...
Boost_1_44_0/
Boost_1_44_0_beta1/
Boost_1_45_0/
Boost_1_45_0_beta1/

> I know it's a volunteer effort; that's why I've tried to do everything I can
> to minimize the workload on those volunteers, by providing detailed reports,
> patches, etc. Part of my frustration is that our voluntary efforts to give
> back to Boost were getting dropped on the floor, along with who knows how
> many others'. If I could check the fixes in myself, I would; I know it's not
> feasible to provide commit access to all and sundry, but the policy of
> granting commit access only to owners of particular libraries seems like it
> may be cutting Boost off from a useful pool of volunteers.

If patches are in trac, they will be addressed eventually.
The key word being eventually.

In Christ,
Steven Watanabe


Boost-users list run by williamkempf at hotmail.com, kalb at libertysoft.com, bjorn.karlsson at readsoft.com, gregod at cs.rpi.edu, wekempf at cox.net