On Tue, 2009-08-18 at 17:53 +0000, John A Meinel wrote:
>
> I expect performance will suck a little bit, as we'll be re-reading
> all
> the files that have a content filter. But at least it won't cause
> bogus
> data to be inserted into the repository on every merge commit.
This would appear to still leave an api in place that isn't content
filter aware.
I appreciate that we need to fix this promptly, but it doesn't seem
complete without fixing / deprecating the get_content_summary api; and
if we fix it commit doesn't need to change.
On Tue, 2009-08-18 at 17:53 +0000, John A Meinel wrote:
>
> I expect performance will suck a little bit, as we'll be re-reading
> all
> the files that have a content filter. But at least it won't cause
> bogus
> data to be inserted into the repository on every merge commit.
This would appear to still leave an api in place that isn't content
filter aware.
I appreciate that we need to fix this promptly, but it doesn't seem
complete without fixing / deprecating the get_content_summary api; and
if we fix it commit doesn't need to change.
-Rob