Re: Patch for major breakage in OAF activation

[Maciej Stachowiak <mjs eazel com>]

Peter Williams <peter@newton.cx> writes:

> It seems a typo got through in the attribute->property transfer...
> I don't know if the oafinfo XML files should specify oaf_attribute
> or oaf_property, but they certainly shouldn't specify oaf_propibute :-)
> 
> I compromise and accept either for now (it'll take a long time for
> existing oafinfo's to get updated.)

Actually, let's leave it at oaf_attribute, I know the lack of matching
is bad but there would be a _lot_ of oafinfo files to upgrade. Or
better yet, let's accept both for now. I just made this change myself
because CVS oaf is broken as it stands but I credited you for catching
it Peter. Thanks!

 - Maciej