Riverbed Cascade Pilot Personal Edition: Take Wireshark to the Next Level - Advanced Triggers and Alerts; Web and VoIP Analytics; Long-Term Trending and Forensics; Deep Packet Analysis with Wireshark

Wireshark-dev: Re: [Wireshark-dev] Add restrictions to arguments of dumpcap

Date Index Thread Index Other Months All Mailing Lists

Date Prev Date Next Thread Prev Thread Next

From: Antoine Reid <antoine.reid@xxxxxxxxx>
Date: Thu, 7 May 2009 15:10:52 -0400

On Thu, May 7, 2009 at 14:34, Nathan Jennings <njen@xxxxxxxxxxxx> wrote:

On 5/7/2009 9:10 AM, Sébastien Tandel wrote:
>[snip]

I had also thought of suggesting ":", but see the overloading problem
now as Stephen D. pointed out... which reminded me of maybe another
potential clash:

How about using an equal sign ? Is there any fear that this could clash with getopt-style long options ?

Antoine

Follow-Ups:
- Re: [Wireshark-dev] Add restrictions to arguments of dumpcap
  - From: Aaron Turner

References:
- [Wireshark-dev] Add restrictions to arguments of dumpcap
  - From: Michael Tüxen
- Re: [Wireshark-dev] Add restrictions to arguments of dumpcap
  - From: Aaron Turner
- Re: [Wireshark-dev] Add restrictions to arguments of dumpcap
  - From: Michael Tüxen
- Re: [Wireshark-dev] Add restrictions to arguments of dumpcap
  - From: Aaron Turner
- Re: [Wireshark-dev] Add restrictions to arguments of dumpcap
  - From: Stephen Donnelly
- Re: [Wireshark-dev] Add restrictions to arguments of dumpcap
  - From: Sébastien Tandel
- Re: [Wireshark-dev] Add restrictions to arguments of dumpcap
  - From: Nathan Jennings

Prev by Date: Re: [Wireshark-dev] Add restrictions to arguments of dumpcap
Next by Date: Re: [Wireshark-dev] Add restrictions to arguments of dumpcap
Previous by thread: Re: [Wireshark-dev] Add restrictions to arguments of dumpcap
Next by thread: Re: [Wireshark-dev] Add restrictions to arguments of dumpcap
Index(es):
- Date
- Thread