Wireshark mailing list archives

Re: [PATCH] Re: Freeing memory of se_alloc'ated object


From: Stephen Fisher <steve () stephen-fisher com>
Date: Tue, 3 May 2011 09:50:51 -0600

On Tue, May 03, 2011 at 04:55:02AM +0400, Max Dmitrichenko wrote:

Anyway, the feature introduced in my patch can be reimplemented. But 
may I ask the dumb question? Who decides here what is going to the 
trunk and what it should like?

Any of the core developers.  But I'm leaving this one up to the more 
experienced core developers.  I'm at 4.5 years and never done much 
serious work in the memory allocation part of Wireshark.

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe


Current thread: