Re: [Wireshark-dev] Why are authors never Cc'ed before their code is changed?

2012-08-23 Thread Pascal Quantin
2012/8/19 Lori Jakab l...@lispmob.org On 08/19/12 06:56, Pascal Quantin wrote: Having a RSS link (or something similar) to the subversion file log ( http://anonsvn.wireshark.org/viewvc/trunk/epan/dissectors/packet-gsmtap.c?view=log for example) could be a way to easily monitor the changes

Re: [Wireshark-dev] Why are authors never Cc'ed before their code is changed?

2012-08-23 Thread Lori Jakab
On 08/23/12 05:52, Pascal Quantin wrote: 2012/8/19 Lori Jakab l...@lispmob.org mailto:l...@lispmob.org On 08/19/12 06:56, Pascal Quantin wrote: Having a RSS link (or something similar) to the subversion file log

Re: [Wireshark-dev] Why are authors never Cc'ed before their code is changed?

2012-08-23 Thread Evan Huus
On Thu, Aug 23, 2012 at 5:23 PM, Lori Jakab lja...@ac.upc.edu wrote: On 08/23/12 05:52, Pascal Quantin wrote: 2012/8/19 Lori Jakab l...@lispmob.org mailto:l...@lispmob.org On 08/19/12 06:56, Pascal Quantin wrote: Having a RSS link (or something similar) to the subversion file log

Re: [Wireshark-dev] Why are authors never Cc'ed before their code is changed?

2012-08-20 Thread Lori Jakab
On 08/19/12 06:56, Pascal Quantin wrote: Having a RSS link (or something similar) to the subversion file log (http://anonsvn.wireshark.org/viewvc/trunk/epan/dissectors/packet-gsmtap.c?view=log for example) could be a way to easily monitor the changes done to a given file for whoever is

Re: [Wireshark-dev] Why are authors never Cc'ed before their code is changed?

2012-08-20 Thread Stephen Fisher
From: lafo...@gnumonks.org 1) Is this the way how the wireshark development model / flow is supposed to work ? Yes. The Wireshark model is that people submit patchs and then the Wireshark core developers become the ongoing maintainers. This seems to have been necessary for a long time

[Wireshark-dev] Why are authors never Cc'ed before their code is changed?

2012-08-19 Thread Harald Welte
Hi all, I understand that different FOSS projects have different cultures, norms, rules, etc. However, my experience with wireshark it has reached a point where I think a post like this is requierd. I don't want to see this as some kind of flame, or to claim that the wireshark development model

Re: [Wireshark-dev] Why are authors never Cc'ed before their code is changed?

2012-08-19 Thread Evan Huus
On Sun, Aug 19, 2012 at 7:03 AM, Harald Welte lafo...@gnumonks.org wrote: Hi all, I understand that different FOSS projects have different cultures, norms, rules, etc. However, my experience with wireshark it has reached a point where I think a post like this is requierd. I don't want to

Re: [Wireshark-dev] Why are authors never Cc'ed before their code is changed?

2012-08-19 Thread Pascal Quantin
2012/8/19 Harald Welte lafo...@gnumonks.org Hi all, I understand that different FOSS projects have different cultures, norms, rules, etc. However, my experience with wireshark it has reached a point where I think a post like this is requierd. I don't want to see this as some kind of

Re: [Wireshark-dev] Why are authors never Cc'ed before their code is changed?

2012-08-19 Thread Sylvain Munaut
Hi Pascal, For me not all changes have the same potential of breakage: a change in an API used by an external tool can easily lead to a complete incompatibility (GSMTAP format unapproved changes for example) while a filter rename or a wrong subtree used to display a field (GMR-1 breakages

Re: [Wireshark-dev] Why are authors never Cc'ed before their code is changed?

2012-08-19 Thread Christopher Maynard
Pascal Quantin pascal.quantin@... writes: 2012/8/19 Harald Welte lafo...@gnumonks.org I agree that this massive filter rename could / should have been discussed before being done The changes that Michael is making regarding filter renaming stems from