Thanks guy. Now it makes sense. It s created by wireshark and not the build. I did not read it right.
On 27 Jan 2015 15:58, "Guy Harris" <
guy@xxxxxxxxxxxx> wrote:
On Jan 27, 2015, at 2:11 AM, Anil <anilkumar911@xxxxxxxxx> wrote:
> Are you sure ? The first line of these files is
>
> # DO NOT EDIT THIS FILE! It was created by Wireshark
The second part of that comment might well be true; somebody might have created it by using Wireshark as the editor.
However, it might also have been manually edited, after having been written out by Wireshark at one point.
The first part is a warning that
1) if you manually edit it while Wireshark is running, and then save color filters, Wireshark might override it (if it's your own color filter file)
and
2) if you don't know what you're doing, you might end up with Wireshark ignoring or complaining about incorrect lines in the file.
> Should this comment be removed ?
It could be removed or replaced, but if somebody who doesn't enjoy manually entering RGB values and manually editing a file whose format was not optimized for human editability decides to edit it with Wireshark (by reading it in as a set of color filters and then writing out the color filters), that comment will be replaced by the "DO NOT EDIT THIS FILE!" comment, so it will return if somebody contributes an updated version of the file that they produced by writing out a file in Wireshark.
___________________________________________________________________________
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