[1.37.0] Jamroot changeset 48493 by Jurko not merged into branches/release?
http://svn.boost.org/trac/boost/changeset/48493 was not merged into branches/release. The comment reads: Minor stylistic changes made to the main Boost library Jamroot file. Corrected several comments. Made searching for header files not search through .svn folders. I'm going to do this merge. In the future, please merge such changes into release rather than relying on the release managers to pick them up. Thanks, --Beman PS: Who is Jerko?
on Mon Oct 20 2008, Beman Dawes <bdawes-AT-acm.org> wrote:
http://svn.boost.org/trac/boost/changeset/48493 was not merged into branches/release. The comment reads: Minor stylistic changes made to the main Boost library Jamroot file. Corrected several comments. Made searching for header files not search through .svn folders.
I'm going to do this merge. In the future, please merge such changes into release rather than relying on the release managers to pick them up.
Hi Beman, How do you distinguish "such changes?" I mean, what characteristics of this particular change indicate that it should have been merged to release? -- Dave Abrahams BoostPro Computing http://www.boostpro.com
On Mon, Oct 20, 2008 at 12:11 PM, David Abrahams <dave@boostpro.com> wrote:
on Mon Oct 20 2008, Beman Dawes <bdawes-AT-acm.org> wrote:
http://svn.boost.org/trac/boost/changeset/48493 was not merged into branches/release. The comment reads: Minor stylistic changes made to the main Boost library Jamroot file. Corrected several comments. Made searching for header files not search through .svn folders.
I'm going to do this merge. In the future, please merge such changes into release rather than relying on the release managers to pick them up.
Hi Beman,
How do you distinguish "such changes?" I mean, what characteristics of this particular change indicate that it should have been merged to release?
I really don't have any useful criteria and am no longer going to run an unmerged changes analysis. --Beman
Beman Dawes wrote:
http://svn.boost.org/trac/boost/changeset/48493 was not merged into branches/release. The comment reads: Minor stylistic changes made to the main Boost library Jamroot file. Corrected several comments. Made searching for header files not search through .svn folders.
I'm going to do this merge. In the future, please merge such changes into release rather than relying on the release managers to pick them up.
This commit was intentionally not merged. Please see my email asking for permission to merge other Jamroot changes. You should not that this commit breaks installing from libs/<some-library>/build directories, so there's a follow-up commit on trunk to fix that -- which was checked in *after* I've merged other Jamroot changes, so decision not to merge 48493 was actually right.
Thanks,
--Beman
PS: Who is Jerko?
Jurko is one of Boost.Build developers. - Volodya
On Mon, Oct 20, 2008 at 3:29 PM, Vladimir Prus <vladimir@codesourcery.com>wrote:
Beman Dawes wrote:
http://svn.boost.org/trac/boost/changeset/48493 was not merged into branches/release. The comment reads: Minor stylistic changes made to the main Boost library Jamroot file. Corrected several comments. Made searching for header files not search through .svn folders.
I'm going to do this merge. In the future, please merge such changes into release rather than relying on the release managers to pick them up.
This commit was intentionally not merged. Please see my email asking for permission to merge other Jamroot changes. You should not that this commit breaks installing from libs/<some-library>/build directories, so there's a follow-up commit on trunk to fix that -- which was checked in *after* I've merged other Jamroot changes, so decision not to merge 48493 was actually right.
Done. Thanks, --Beman
participants (3)
-
Beman Dawes -
David Abrahams -
Vladimir Prus