Don't have -M affect -v yet; if we end up, for example, having dumpcap

being the only program that needs to be linked with *pcap, that's when
we'd want to fetch that information, but there might be other libraries
(e.g., the POSIX capabilities library) that it might be linked with but
that programs that use it aren't linked with.

Don't commit to the output formats of -M, as they are, as noted, subject
to change from release to release.

svn path=/trunk/; revision=32904

1 files changed, 3 insertions, 9 deletions

diff --git a/doc/dumpcap.pod b/doc/dumpcap.pod
index f49c79d397..681e6d23d4 100644
--- a/doc/dumpcap.pod
+++ b/doc/dumpcap.pod
@@ -191,15 +191,9 @@ link types can be used for the B<-y> option.
 
 =item -M
 
-When used with B<-v>, B<-D>, B<-L> and B<-S>, print machine-readable
-output.  The machine-readable output of B<-v> gives only the
-libpcap/WinPcap version information; the machine-readable output of
-B<-D> gives additional per-interface information; the machine-readable
-output of B<-L> gives additional interface capability information and
-additional per-link-layer-type information; the machine-readable output
-of B<-S> doesn't print the column headers.  The machine-readable output
-is intended to be read by B<Wireshark> and B<TShark>; its format is
-subject to change from release to release.
+When used with B<-D>, B<-L> and B<-S>, print machine-readable output. 
+The machine-readable output is intended to be read by B<Wireshark> and
+B<TShark>; its format is subject to change from release to release.
 
 =item -n