Am Montag, 11. September 2006 15:01 schrieben Sie: Hi ken,
> > patch as we intend to provide more incremental patches in the future and > > we aim to make your work as easy as possible. > > I will try to look at it this week. Did you have an opportunity to look at it in the meantime? Is there anything we can do to help the process? The patch https://bugzilla.andrew.cmu.edu/attachment.cgi?id=459&action=view also fixes the shortcoming as reported by Alexandros Vellis. > I have other pressing business to > take care of first. I'm not sure that we need to keep the old LISTEXT > code, since it was a compile-time option and I doubt that any clients > are using it, but I'll have to think about it some more. I agree that we should not encourage anyone to built upon an outdated features. What about keeping the old LISTEXT capability for 2.3 but declaring it officially deprecated in the release notes and the documentation and then remove it in a later major release? In addition we can reflect this state in the name of the configure switch. - --enable-listext + --enable-legacy-listext IMHO this would give potential users a little bit more time and allow them to adapt their clients to the new uptodate LIST-EXTENDED capability. LIST-EXTENDED is the prerequisite in order to be able to contribute uptodate METADATA/annotations support to Cyrus Imapd Regards, -- martin -- http://www.erfrakon.com/ Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker
