[Wireshark-dev] buildbot failure in Wireshark (development) on Ubuntu-10.04-x64

2011-07-04 Thread buildbot-no-reply
The Buildbot has detected a new failure of Ubuntu-10.04-x64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Ubuntu-10.04-x64/builds/1664 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: ubuntu-10.04-x64 Build

[Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.6-x64

2011-07-04 Thread buildbot-no-reply
The Buildbot has detected a new failure of OSX-10.6-x64 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/OSX-10.6-x64/builds/3188 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.6-x64 Build Reason: Bui

[Wireshark-dev] buildbot failure in Wireshark (development) on Clang-Code-Analysis

2011-07-04 Thread buildbot-no-reply
The Buildbot has detected a new failure of Clang-Code-Analysis on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/Clang-Code-Analysis/builds/248 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: clang-code-analysis

[Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-PowerPC

2011-07-04 Thread buildbot-no-reply
The Buildbot has detected a new failure of OSX-10.5-PowerPC on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/OSX-10.5-PowerPC/builds/3123 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-ppc Build Reas

[Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-x86

2011-07-04 Thread buildbot-no-reply
The Buildbot has detected a new failure of OSX-10.5-x86 on Wireshark (development). Full details are available at: http://buildbot.wireshark.org/trunk/builders/OSX-10.5-x86/builds/3611 Buildbot URL: http://buildbot.wireshark.org/trunk/ Buildslave for this Build: osx-10.5-x86 Build Reason: Bui

Re: [Wireshark-dev] [Wireshark-commits] rev 37859: /trunk/ /trunk/gtk/: color_dlg.c /trunk/: color_filters.c color_filters.h

2011-07-04 Thread Stig Bjørlykke
On Mon, Jul 4, 2011 at 5:49 PM, Sake Blok wrote: > Where do you need that info, in the frame section of the packet details we > list the following: > > Coloring Rule Name: ___tmp_color_filter___01 If a user wants to know which coloring rule is used for a selected package, the "Coloring Rule Name

Re: [Wireshark-dev] [Wireshark-commits] rev 37859: /trunk/ /trunk/gtk/: color_dlg.c /trunk/: color_filters.c color_filters.h

2011-07-04 Thread Sake Blok
On 4 jul 2011, at 17:57, Guy Harris wrote: > > On Jul 4, 2011, at 8:49 AM, Sake Blok wrote: > >> Where do you need that info, in the frame section of the packet details we >> list the following: >> >> Coloring Rule Name: ___tmp_color_filter___01 >> Coloring Rule String: (ip.addr eq 192.168.0.1

Re: [Wireshark-dev] [Wireshark-commits] rev 37859: /trunk/ /trunk/gtk/: color_dlg.c /trunk/: color_filters.c color_filters.h

2011-07-04 Thread Guy Harris
On Jul 4, 2011, at 8:49 AM, Sake Blok wrote: > Where do you need that info, in the frame section of the packet details we > list the following: > > Coloring Rule Name: ___tmp_color_filter___01 > Coloring Rule String: (ip.addr eq 192.168.0.104 and ip.addr eq > 208.117.232.170) and (tcp.port eq

Re: [Wireshark-dev] [Wireshark-commits] rev 37859: /trunk/ /trunk/gtk/: color_dlg.c /trunk/: color_filters.c color_filters.h

2011-07-04 Thread Sake Blok
On 4 jul 2011, at 17:22, Stig Bjørlykke wrote: > 2011/7/4 Sake Blok : >> Conversation coloring is just one of the sources of these temporary coloring >> filters. Rightclicking on any field can also create a temporary coloring >> rule. IMHO it is the fact that these coloring rules don't get saved

Re: [Wireshark-dev] [Wireshark-commits] rev 37859: /trunk/ /trunk/gtk/: color_dlg.c /trunk/: color_filters.c color_filters.h

2011-07-04 Thread Stig Bjørlykke
2011/7/4 Sake Blok : > Conversation coloring is just one of the sources of these temporary coloring > filters. Rightclicking on any field can also create a temporary coloring > rule. IMHO it is the fact that these coloring rules don't get saved to the > colorfilters file that makes them distinct

Re: [Wireshark-dev] [Wireshark-commits] rev 37859: /trunk/ /trunk/gtk/: color_dlg.c /trunk/: color_filters.c color_filters.h

2011-07-04 Thread Sake Blok
On 1 jul 2011, at 23:13, s...@wireshark.org wrote: > http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=37859 > > User: stig > Date: 2011/07/01 02:13 PM > > Log: > Renamed "___tmp_color_filter___" to "___conversation_color_filter___" > in the coloring rule name to better describe w