Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-bugs: [Wireshark-bugs] [Bug 1145] Build information not presented when viewing a bug report

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 3 Oct 2006 17:57:59 +0000 (GMT)

http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1145


gerald@xxxxxxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




------- Comment #1 from gerald@xxxxxxxxxxxxx  2006-10-03 17:57 GMT -------
Bugzilla's custom template feature implementation deviates from the
documentation slightly.  The build info should work for new bugs, but it looks
like the information wasn't collected for previously-entered bugs (including
this one) and has been lost.


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  • References:
    • [Wireshark-bugs] [Bug 1145] New: Build information not presented when viewing a bug report
      • From: bugzilla-daemon
  • Prev by Date: [Wireshark-bugs] [Bug 1147] Build information test.
  • Next by Date: [Wireshark-bugs] [Bug 212] Ethereal crashes after I clicked on "Edit -> Preferences"
  • Previous by thread: [Wireshark-bugs] [Bug 1145] New: Build information not presented when viewing a bug report
  • Next by thread: [Wireshark-bugs] [Bug 1146] New: Various instances of wireshark reading from various named pipes -> closing error
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation