Rev 4191: Correct logic for detecting when to use record_iter_changes in commit. in http://people.ubuntu.com/~robertc/baz2.0/integration

[Robert Collins]

At http://people.ubuntu.com/~robertc/baz2.0/integration

------------------------------------------------------------
revno: 4191
revision-id: robertc at robertcollins.net-20090327043658-vzfmwbuhd7pam1m7
parent: robertc at robertcollins.net-20090327041025-rgutx4q03xo4pq6l
committer: Robert Collins <robertc at robertcollins.net>
branch nick: integration
timestamp: Fri 2009-03-27 15:36:58 +1100
message:
  Correct logic for detecting when to use record_iter_changes in commit.
=== modified file 'bzrlib/commit.py'
--- a/bzrlib/commit.py	2009-03-27 04:10:25 +0000
+++ b/bzrlib/commit.py	2009-03-27 04:36:58 +0000
@@ -292,7 +292,8 @@
             not self.specific_files and
             not self.exclude and 
             not self.branch.repository._format.supports_tree_reference and
-            self.branch.repository._format.fast_deltas or len(self.parents) < 2)
+            (self.branch.repository._format.fast_deltas or
+             len(self.parents) < 2))
         self.pb = bzrlib.ui.ui_factory.nested_progress_bar()
         self.basis_revid = self.work_tree.last_revision()
         self.basis_tree = self.work_tree.basis_tree()