Hi,

* Bert Wesarg wrote (2008-03-04 23:17):
>Thanks.
>
>On Tue, Mar 4, 2008 at 9:51 PM, Thorsten Haude <[EMAIL PROTECTED]> wrote:
>>     Bugs introduced after the last release should get special consideration.
>Here is my list, which should be committed/considered/discussed:

All these were introduced after the last release?


> 1. smartIndent.c: remove static

Not even worth discussing IMHO, just remove them.


> 2. #1894726 fix memory leak in PromoteToGlobal()

Fixed.


> 3. #1888195 calltip's ID not returned correctly
>    I haven't tested this throughly yet, but I will.
>    And maybe my follow-up patch from patch #1633136, which shows only
>the 'not fount'-
>    calltip from the menu action, but not from the calltip()-macro

I think this is a bit more interesting. I worked on calltips for the
Patch Collection, and I think there are some minor changes which would
greatly improve usefulness of the calltips. However, I would prefer to
do this after the release.


> 4. #1907176 Empty $file_path

Since it is easy to fix...


> 5. #1869948 {forward,backward}_paragraph() broken with multi blank lines
>    this isn't really release critical, but the problem is real and
>    the patch is simple (if you remove most of the small style changes)

Looks simple enough, I agree.


>      #1869862 "^" doesn't match all lines
>      Has a patch, but can someone confirm its correctness!

Anyway, I think we should commit it.


>Do we need pre-built binaries at the time the source release is made?

This is the usual process. I thought that the release would be quicker
if a known process would be used. In general, I think that we could
collect binaries after the source release.


Thorsten
-- 
I am an engineer, scientist and hacker at heart, and because
of the DMCA and patent laws I am forced to be a criminal to
continue to invent, engineer and think.
    - Anonymous Coward

Attachment: pgpH3zKpnIijG.pgp
Description: PGP signature

-- 
NEdit Develop mailing list - [email protected]
http://www.nedit.org/mailman/listinfo/develop

Reply via email to