Re: [Wireshark-dev] 4.2.0 release schedule

2023-09-17 Thread Jaap Keuter
Hi, This starts to resemble the Linux kernel merge window challenges. There's always a tradeoff between ease of development vs. churn. Things do need to settle down before a branch can be made, that's what we're here for. Personally I'm in the process of finalizing a new dissector (for iperf3)

Re: [Wireshark-dev] 4.2.0 release schedule

2023-09-17 Thread João Valverde
I'm not sure I follow. I don't know why things would settle down before a branch is made. That's exactly my point, the master branch should be unaffected by the release schedule IMO. Things settle down after the branch is created, not before. If the policy I outline before is followed there's

Re: [Wireshark-dev] Wireshark-dev Digest, Vol 208, Issue 2

2023-09-17 Thread John Thacker
On Thu, Sep 14, 2023 at 12:52 PM John Dill wrote: > >Message: 2 > >Date: Tue, 12 Sep 2023 10:24:19 -0400 > >From: John Thacker > >To: Developer support list for Wireshark > >Subject: Re: [Wireshark-dev] question on validation of a dissected > >string from a BASE_CUSTOM hf item > >Messag

Re: [Wireshark-dev] question on validation of a dissected string from a BASE_CUSTOM hf item

2023-09-17 Thread Guy Harris
On Sep 7, 2023, at 9:15 AM, John Dill wrote: > I have a question whether I can get the dissected string of the BASE_CUSTOM > header field so that I can do analysis on it and convert it to floating point > to do range analysis so I can issue an expert info if the value is valid but > out of ran