One feature of Linux's sgid-folders is that creating a nested folder automatically makes that folder setgid too. Since we can't set the sgid bit after doing a chmod, we lose that marker. For example, creating a deeply nested tree, we wouldn't have any sgid folders except the very top one, and we'd have to walk up toward the root, looking for a sgid folder, to see if we should change the group. Anyone not using bazaar to access the subtree would probably mess it up.
Interestingly, while trying this out, I found out that OSX and, apparently, all BSDs don't have a meaning for sgid on folders because they *always* make a folder's group equal to the parent folder's group. If bazaar followed that logic, we could ignore the sgid problem.
One feature of Linux's sgid-folders is that creating a nested folder automatically makes that folder setgid too. Since we can't set the sgid bit after doing a chmod, we lose that marker. For example, creating a deeply nested tree, we wouldn't have any sgid folders except the very top one, and we'd have to walk up toward the root, looking for a sgid folder, to see if we should change the group. Anyone not using bazaar to access the subtree would probably mess it up.
Interestingly, while trying this out, I found out that OSX and, apparently, all BSDs don't have a meaning for sgid on folders because they *always* make a folder's group equal to the parent folder's group. If bazaar followed that logic, we could ignore the sgid problem.