Index: epan/dissectors/packet-btl3cap.c
===
--- epan/dissectors/packet-btl2cap.c(revision 38619)
+++ epan/dissectors/packet-btl2cap.c(working copy)
@@ -1466,52 +1466,52 @@
},
{ &hf_btl2cap_info_f
Please submit patches by opening a bug at https://bugs.wireshark.org/ so
they don't get lost? Thanks.
___
Sent via:Wireshark-dev mailing list
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https:/
Hi, I feel that opening bug for a simple patch is too much overhead.
Cannot this be managed like it is done in linux kernel?
On Fri, Aug 19, 2011 at 6:49 PM, Stephen Fisher
wrote:
> Please submit patches by opening a bug at https://bugs.wireshark.org/ so
> they don't get lost? Thanks.
>
Hi,
We're not the Linux kernel, hence we have to find our own way forward.
We found that too many patches were lost in the email archives for
various reasons.
For instance we don't have paid for staff(1) working the project,
unlike the Linux kernel.
The (severely) time constrained volunteers ag
Jaap Keuter writes:
> We're not the Linux kernel, hence we have to find our own way forward.
> We found that too many patches were lost in the email archives for
> various reasons.
> > On Fri, Aug 19, 2011 at 6:49 PM, Stephen Fisher
> > wrote:
> >
> >> Please submit patches by opening a bug at
Hi Chris,
On Tue, Aug 23, 2011 at 4:36 AM, Chris Maynard
wrote:
> Jaap Keuter writes:
>
>> We're not the Linux kernel, hence we have to find our own way forward.
>> We found that too many patches were lost in the email archives for
>> various reasons.
>
>> > On Fri, Aug 19, 2011 at 6:49 PM, Step
Hi,
On Mon, Aug 22, 2011 at 4:13 PM, Jaap Keuter wrote:
> Hi,
>
> We're not the Linux kernel, hence we have to find our own way forward.
> We found that too many patches were lost in the email archives for various
> reasons.
> For instance we don't have paid for staff(1) working the project, unli
Hi,
On Tue, 23 Aug 2011 10:27:35 +0300, Andrei Emeltchenko wrote:
Hi,
On Mon, Aug 22, 2011 at 4:13 PM, Jaap Keuter wrote:
Hi, We're not the Linux kernel, hence we have to find our own way
forward. We found that too many patches were lost in the email
archives
for various reasons. For insta
