https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15984
--- Comment #13 from Jaap Keuter <jaap.keu...@xs4all.nl> ---
(In reply to tinker from comment #12)
> (In reply to Alexis La Goutte from comment #11)
> > (In reply to tinker from comment #10)
> > > (In reply to Alexis La Goutte from comment #9)
> > > > Hi tinker,
> > > >
> > > > Sorry, too busy actually and Chrome (and Google) will be switch soon on
> > > > IETF
> > > > QUIC
> > >
> > > Thank you for reply, If I have strong willing to parse Q046, can I update
> > > the gquic dissect code and patch to trunk?
> > Yes
> > >
> > > By the way, I have found that there is already a patch code provided by
> > > Greg
> > > below which you could find in
> > > https://bugs.wireshark.org/bugzilla/attachment.cgi?id=17275&action=edit
> > >
> > > Why this patch not be commited and merged?
> > No push on Gerrit and it is not complete
>
> ok, so if someone want to use wireshark to parse gquic q046, is it
> recommeded to update compelte parse code in gquic dissect by himself and
> submit it to trunk?
That is how a community driven project works, yes.
--
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
