From: Richard Sharpe <realrichardsharpe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
Cc: Guy Harris <guy-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>,
radiotap-S783fYmB3Ccdnm+yROfE0A@public.gmane.org,
Gerald Combs <gerald-IZ8446WsY0/dtAWm4Da02A@public.gmane.org>
Subject: Re: [RFA] HE support
Date: Thu, 12 Apr 2018 06:56:02 -0700 [thread overview]
Message-ID: <CACyXjPzvxWOHa_1QBmSsE7EvVB=Xr1A27EqTybbj=ggmsAeO+A@mail.gmail.com> (raw)
In-Reply-To: <1523526947.12930.8.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
On Thu, Apr 12, 2018 at 2:55 AM, Johannes Berg
<johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org> wrote:
> On Thu, 2018-04-12 at 02:54 -0700, Guy Harris wrote:
>>
>> > What do you think? Could wireshark do a point release of 2.6.x and 2.5.x
>> > to include the changes? Or perhaps we could just say that 2.5.x would
>> > just be broken for this, and people should upgrade for HE?
>>
>>
>> n.{odd number}.x Wireshark releases are development releases; Gerald,
>> is there any reason to care whether 2.5.x is broken when it tries to
>> read this radiotap field?
>
> Ah, I wasn't aware of this, thanks.
>
>> 2.6.0 is scheduled for April 18th; Gerald, if we have a finalized
>> version of this radiotap field soon, would it be possible to get a
>> change for that into the 2.6.0 release?
>
> That's pretty soon, but another option would be to just #if 0 the broken
> code quickly? That's a bit annoying, but better than shipping something
> that we may have to break.
I can go with either approach ... coding the changes will not take
long :-) Sigh. The perils of trying to stay at the front if the
charge.
--
Regards,
Richard Sharpe
(何以解憂?唯有杜康。--曹操)(传说杜康是酒的发明者)
prev parent reply other threads:[~2018-04-12 13:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 8:25 [RFA] HE support Johannes Berg
[not found] ` <1517300719.2189.51.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2018-02-20 9:37 ` Johannes Berg
[not found] ` <1519119420.16723.26.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2018-02-20 13:01 ` Johannes Berg
[not found] ` <1519131691.16723.35.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2018-02-20 14:59 ` Richard Sharpe
[not found] ` <CACyXjPxQLN3iiCjVu5X5ZQUMGBEY9FyM9dnPmEiT7XQnaUhjEQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-20 15:06 ` Johannes Berg
2018-02-20 16:05 ` Richard Sharpe
2018-02-20 16:42 ` Johannes Berg
[not found] ` <1519144938.16723.42.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2018-02-22 11:13 ` Johannes Berg
2018-04-12 9:35 ` Johannes Berg
[not found] ` <1523525707.12930.6.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2018-04-12 9:54 ` Guy Harris
[not found] ` <9FE36B35-5238-436D-9B5A-342C92D20701-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
2018-04-12 9:55 ` Johannes Berg
[not found] ` <1523526947.12930.8.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2018-04-12 13:56 ` Richard Sharpe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACyXjPzvxWOHa_1QBmSsE7EvVB=Xr1A27EqTybbj=ggmsAeO+A@mail.gmail.com' \
--to=realrichardsharpe-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=gerald-IZ8446WsY0/dtAWm4Da02A@public.gmane.org \
--cc=guy-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org \
--cc=johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org \
--cc=radiotap-S783fYmB3Ccdnm+yROfE0A@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).