The bug was marked as Resolved/Fixed in March. That means the code is present in the 1.4.0 release that came out recently.
Sourabh Rathor wrote: > > Hi Developers, > > Any idea about when we can expect this bug to be in the final release of > Wireshark ??? > This is being resolved in March'10 itself. > > Thanks In Advance, > Sourabh Rathor > > On Wed, Mar 17, 2010 at 7:55 PM, Sourabh Rathor > <sourabhrathor2...@gmail.com <mailto:sourabhrathor2...@gmail.com>> wrote: > > Hi > > Please provide comment to the new dissector written (Bug 4591 > <https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4591>). > > -- > Sourabh Rathor > Institute Of Informatics & Communication > South Campus, Delhi University > > > > > > > ------------------------------------------------------------------------ > > ___________________________________________________________________________ > 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-requ...@wireshark.org?subject=unsubscribe ___________________________________________________________________________ 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-requ...@wireshark.org?subject=unsubscribe
