Wireshark-dev: Re: [Wireshark-dev] PATCH: btl2cap extended window shows wrong bit
Hi,
On Mon, Aug 22, 2011 at 4:13 PM, Jaap Keuter <jaap.keuter@xxxxxxxxx> 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, unlike the
> Linux kernel.
This is misunderstanding IMO. People get paid indirectly. I use tools,
I submit patch and I am not paid for that. But I still get my salary.
> The (severely) time constrained volunteers agreed to resort to other ways to
> capture patches: bugzilla.
If we would use git then the patches would contain commit message and
authors info
so it would ne much easy to track it. Many big project manage with git
and mailing list
and this is much easier and less time consuming.
> So, you are free to leave your patch on the mailing list, but i could get
> lost.
I have submitted several bugs with patches some time ago (concerning
bluetooth) and most of them got lost :-(
Regards,
Andrei
> That is not to say that it will be applied straight away otherwise, but then
> we're back to the time constrained volunteers...
>
> Thanks,
> Jaap
>
>
> (1) I hope Gerald receives a pay check now and then of course, but he's got
> more on his plate in facilitating the project in more ways than you can
> imagine. He even puts in a few lines of code now and then ;)
>
>
> On Mon, 22 Aug 2011 11:14:01 +0300, Andrei Emeltchenko wrote:
>
>> 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.
>>>
>>
>
> ___________________________________________________________________________
> 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
>
