1.6.6 isn't scheduled yet, but it's been a couple of months since 1.6.5
which would imply that it shouldn't be too much longer.
vijay wrote:
Is it possible to tell how longer would it be before Wireshark 1.6.6 is
released ?
On Mon, Mar 5, 2012 at 1:31 AM, Guy Harris <guy@xxxxxxxxxxxx
<mailto:guy@xxxxxxxxxxxx>> wrote:
On Mar 4, 2012, at 8:24 PM, Jeff Morriss wrote:
> https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5939
>
> It's scheduled to be fixed in 1.6.6.
...and I backported the relevant part (a tiny fraction of the change
responsible for fixing it in the trunk; that change added a bunch of
new functionality, so it's not appropriate for the 1.6 branch in its
entirety) to 1.6 and checked it in.
I've also scheduled that change for the 1.4 branch.
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx
<mailto:wireshark-dev@xxxxxxxxxxxxx>>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx
<mailto:wireshark-dev-request@xxxxxxxxxxxxx>?subject=unsubscribe
------------------------------------------------------------------------
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
