ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] Query

From: Anders Broman <anders.broman@xxxxxxxxxxxx>
Date: Thu, 1 Mar 2012 12:43:11 +0100
Hi,
It can be an advantage to submit in smaller steps to get those reviewed and any quirks ironed out rather than submitting a huge fulfledged dissector.
Regards
Anders


From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Alexis La Goutte
Sent: den 1 mars 2012 12:31
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Query

Hi,

Sur ! it is not a problem ! :-)

Regards

On Thu, Mar 1, 2012 at 12:11 PM, Tyson Key <tyson.key@xxxxxxxxx> wrote:
Hi Krishnamurthy,

Whilst I'm not a core developer, I don't see why that would be a
problem. (In fact, that's how I submitted some of my own dissectors).

Tyson.

On 1 March 2012 03:01, Krishnamurthy Mayya <krishnamurthymayya@xxxxxxxxx> wrote:
> Hi all,
> Is it ok if we create a new bug in wireshark bugzilla to say that we are
> working on writing the decoding module for these protocols and attach the
> patches, packets after we are done with it??
> I just wanted to avoid the duplicate work getting done by many. I am
> currently working on writing the decoding modules based on few RFCs and will
> actually take some time to submit it back.
>
> Thanks in advance for the reply.
>
> Thanks and regards
> Krishnamurthy Mayya
>
> ___________________________________________________________________________
> 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



--
                                          Fight Internet Censorship!
http://www.eff.org
http://vmlemon.wordpress.com | Twitter/FriendFeed/Skype: vmlemon |
00447934365844
___________________________________________________________________________
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