Hi Martin, I see Jaap has posted some comments about the dissector "patch".
After you have fixed that, if you are sure that you will change the code in the very near future, you can just put a note in the bug saying that the current patch should not be committed as you are working on a reworked one. Someone might still look at the existing patch and point out something which was seriously wrong. When you upload that patch you will have the option of marking the current one obsolete. Or, you could continue reworking the dissector while you wait for this one to be committed. If the current patch is not committed by the time you have reworked the dissector (and that can happen), you can follow the above procedure. If the bug is closed by then, you should ideally open a new one. Best regards, Abhik. On Tue, Jul 8, 2008 at 1:20 AM, Martin Corraine (mcorrain) <[EMAIL PROTECTED]> wrote: > Hello, > > I'm new to this so I want to make sure that I submitted my ged125 dissector > properly. It is bug # 2692. Also, I will probably make changes to this > dissector in the near future as Cisco uses this. I did fuzz test but there > are a few parts that couldn't be well tested at this moment. Is there an > easy way I can quickly modify the sources I submitted without going through > reporting a bug since I'm the only original author of the dissector? > > Thanks, > Martin > _______________________________________________ > Wireshark-dev mailing list > Wireshark-dev@wireshark.org > https://wireshark.org/mailman/listinfo/wireshark-dev > > _______________________________________________ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
