aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDario Lombardo <lomato@gmail.com>2018-03-31 12:55:44 +0200
committerAnders Broman <a.broman58@gmail.com>2018-04-02 06:29:33 +0000
commit9dde6d4b5fa6ba3312e3e3bff940a148b68cfba9 (patch)
treef8849e0b15747294e42406b29afa02183a4d6bc0
parentc9904986f7c52857bed8bb72bbe61b39c8f8de12 (diff)
doc: minor changes in README files.
Change-Id: I5b21ade727f9c4bed6545e69d87082baafaefa2b Reviewed-on: https://code.wireshark.org/review/26702 Reviewed-by: Anders Broman <a.broman58@gmail.com>
-rw-r--r--doc/README.design3
-rw-r--r--doc/README.developer2
-rw-r--r--doc/README.dissector2
-rw-r--r--doc/README.stats_tree4
4 files changed, 3 insertions, 8 deletions
diff --git a/doc/README.design b/doc/README.design
index 7b9fc586cc..e35cbd0f78 100644
--- a/doc/README.design
+++ b/doc/README.design
@@ -52,7 +52,6 @@ routine that goes through all the packets in the capture; the loop does
}
-The "wtap_seek_read()" call read the packet data into memory; the
+The "wtap_seek_read()" call reads the packet data into memory; the
"epan_dissect_new()" call "dissects" that data, building a tree
structure for the fields in the packet.
-
diff --git a/doc/README.developer b/doc/README.developer
index e494e9e7b9..6d2872a5cd 100644
--- a/doc/README.developer
+++ b/doc/README.developer
@@ -1,5 +1,3 @@
-Tabsize: 4
-
This file is a HOWTO for Wireshark developers. It describes general development
and coding practices for contributing to Wireshark no matter which part of
Wireshark you want to work on.
diff --git a/doc/README.dissector b/doc/README.dissector
index e2aa2e10fc..778ef0775f 100644
--- a/doc/README.dissector
+++ b/doc/README.dissector
@@ -1,5 +1,3 @@
-Tabsize: 4
-
This file is a HOWTO for Wireshark developers interested in writing or working
on Wireshark protocol dissectors. It describes expected code patterns and the
use of some of the important functions and variables.
diff --git a/doc/README.stats_tree b/doc/README.stats_tree
index 24d4479945..cb276f3897 100644
--- a/doc/README.stats_tree
+++ b/doc/README.stats_tree
@@ -111,7 +111,7 @@ the stats_tree API
every stats_tree callback has a stats_tree* parameter (st), stats_tree is an obscure
data structure which should be passed to the api functions.
-stats_tree_register( tapname, abbr, name, flags, packet_cb, init_cb, cleanup_cb);
+stats_tree_register(tapname, abbr, name, flags, packet_cb, init_cb, cleanup_cb);
registers a new stats tree
stats_tree_register_plugin(tapname, abbr, name, flags, packet_cb, init_cb, cleanup_cb);
@@ -210,6 +210,6 @@ stat_node_clear_flags functions. Currently these flags are defined:
bottom half. Each half is sorted normally. Top always appear
first :)
-You can find more examples of these in $srcdir/plugins/stats_tree/pinfo_stats_tree.c
+You can find more examples of these in $srcdir/plugins/epan/stats_tree/pinfo_stats_tree.c
Luis E. G. Ontanon.