From ca78bc40b2f05ad8f45d0fd08ad0650421eb32bc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jurko=20Gospodneti=C4=87?= Date: Wed, 18 Jul 2012 13:26:02 +0000 Subject: [PATCH] Minor stylistic changes made to the Python Boost Build comment updated in the previous commit. [SVN r79582] --- src/build/virtual_target.py | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/src/build/virtual_target.py b/src/build/virtual_target.py index b0e1ffbb4..908e53192 100644 --- a/src/build/virtual_target.py +++ b/src/build/virtual_target.py @@ -809,12 +809,12 @@ class Action: # when an actual Boost Jam action is encountered while we do this even # if our Boost Build action is actually modeling a rule that will then # register one or more Boost Jam actions. In that case our INCLUDES - # relation added here will affect the build behaviour but it will not be - # solving any actual problem. The only thing it might seem like it is - # doing is forcing multiple separate actions to be run all together or - # none at all but it will not do that completely either - it would miss - # the case when one of the action targets depends on a target that needs - # to be updated and another does not. + # relation added here will affect the build behaviour but it will no + # be solving any actual problem. The only thing it might seem like it + # is doing is forcing multiple separate actions to be run all together + # or none at all but it will not do that completely either - it would + # miss the case when one of the action targets depends on a target that + # needs to be updated and another does not. if len(actual_targets) > 1: bjam.call("INCLUDES", actual_targets, actual_targets)