Joerg Mayer wrote:
On Wed, Mar 14, 2007 at 09:58:26AM +0100, Sake Blok wrote:
I have not seen many
patches being overlooked actually. There were the occasions where a review
lasted a little longer, but most patches were commited within a couple of
days. Maybe a patch-tracking system is a
that names networks / subnets - Bug
1445
Cheers
Doug
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Joerg Mayer
Sent: 14 March 2007 15:08
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Query on status of patches
On Wed, Mar 14
list for Wireshark wireshark-dev@wireshark.org
Sent: Sunday, March 11, 2007 7:00 PM
Subject: Re: [Wireshark-dev] Query on status of patches
Hi,
I completely agree with Jaap with the view of making committers
'responsible' for different parts of wireshark. It is not viable.
I however don't
On Wed, Mar 14, 2007 at 09:58:26AM +0100, Sake Blok wrote:
I have not seen many
patches being overlooked actually. There were the occasions where a review
lasted a little longer, but most patches were commited within a couple of
days. Maybe a patch-tracking system is a little overkill. The
Joerg Mayer wrote:
On Wed, Mar 14, 2007 at 09:58:26AM +0100, Sake Blok wrote:
I have not seen many
patches being overlooked actually. There were the occasions where a review
lasted a little longer, but most patches were commited within a couple of
days. Maybe a patch-tracking system is a
Joerg Mayer wrote:
Hmm, I don't understand which part wouldn't work. Stage 1 of submitting
a patch is to send it to the ml - in most cases, the patch will be
submitted/commented on quickly. In those cases, where this doesn't work
open a bug and attach the patch. That has worked fine in the
On 3/11/07, Sebastien Tandel [EMAIL PROTECTED] wrote:
I however don't think that's a reason to reject the idea of a patch
tracker system. I think there are some advantages, and for both sides
without imposing mandatory responsibilities for anyone :
I don't know the specifics of the
I know it is very frustrating when pathces and ideas are being ignored.
Please, for many of the developers of wireshark, wireshark is only an
interesting hobby for which time to commit is very limited.
Life and work situations affect time being available. This
unfortuantely results in situations
!
Cheers
Doug
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of ronnie
sahlberg
Sent: 09 March 2007 09:40
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Query on status of patches
I know it is very frustrating when pathces and ideas
Hi guys
I submitted two patches earlier this year:
31 January 2007 - User can select dissector based on packet matching
display filter
13 February 2007 - TShark input and output options
Can anybody tell me their current status? That is:
- Are they queued waiting for review?
- Are
Douglas Pratley wrote:
I submitted two patches earlier this year:
...
Can anybody tell me their current status? That is:
To follow up what Doug has said, I have to say that I've found my recent
experiences in getting patches applied less than positive. Anders
applied quite a few, but there
Hi,
I can see your frustration. You like to be appreciated for the work done
on creating a feature/patch you want to share with the world. That is what
OSS is all about. On the other hand the project owner' has to walk a
fine line, getting enough committers in, who don't get compensation, while
12 matches
Mail list logo
