diff options
author | Guy Harris <guy@alum.mit.edu> | 2017-03-28 03:21:18 -0700 |
---|---|---|
committer | Guy Harris <guy@alum.mit.edu> | 2017-03-28 10:21:50 +0000 |
commit | ed3b5e5764ce368edc6ca10b81411a7b01b29444 (patch) | |
tree | 65714bdb257e950042a712be4a90da229a4c3536 /doc | |
parent | 8f515b1a99d0043966a8d287cee38fe67e06d189 (diff) | |
download | wireshark-ed3b5e5764ce368edc6ca10b81411a7b01b29444.tar.gz |
Get rid of blanks at the ends of lines.
Change-Id: I10a756a4a42d4f27f59e12c11f12d71947191c92
Reviewed-on: https://code.wireshark.org/review/20760
Reviewed-by: Guy Harris <guy@alum.mit.edu>
Diffstat (limited to 'doc')
-rw-r--r-- | doc/README.dissector | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/doc/README.dissector b/doc/README.dissector index f3b1d61897..41297df7ae 100644 --- a/doc/README.dissector +++ b/doc/README.dissector @@ -1602,35 +1602,35 @@ encodings that are currently supported are: the UN*X epoch (1970-01-01 00:00:00 UTC) and the next 4 bytes are nanoseconds since that second. (I.e., a UN*X struct timespec with a 4-byte time_t.) - + ENC_TIME_NTP - 8 bytes; the first 4 bytes are seconds since the NTP epoch (1901-01-01 00:00:00 GMT) and the next 4 bytes are 1/2^32's of a second since that second. (I.e., a 64-bit count of 1/2^32's of a second since the NTP epoch, with the upper 32 bits first and the lower 32 bits second, even when little-endian.) - + ENC_TIME_TOD - 8 bytes, as a count of microseconds since the System/3x0 and z/Architecture epoch (1900-01-01 00:00:00 GMT). - + ENC_TIME_RTPS - 8 bytes; the first 4 bytes are seconds since the UN*X epoch and the next 4 bytes are are 1/2^32's of a second since that second. (I.e., it's the offspring of a mating between UN*X time and NTP time.) It's used by the Object Management Group's Real-Time Publish-Subscribe Wire Protocol for the Data Distribution Service. - + ENC_TIME_TIMEVAL - 8 bytes; the first 4 bytes are seconds since the UN*X epoch and the next 4 bytes are microseconds since that second. (I.e., a UN*X struct timeval with a 4-byte time_t.) - + ENC_TIME_SECS - 4 to 8 bytes, representing a value in seconds since the UN*X epoch. - + ENC_TIME_MSECS - 6 to 8 bytes, representing a value in milliseconds since the UN*X epoch. - + ENC_TIME_SECS_NTP - 4 bytes, representing a count of seconds since the NTP epoch. (I.e., seconds since the NTP epoch.) - + ENC_TIME_RFC_3971 - 8 bytes, representing a count of 1/64ths of a second since the UN*X epoch; see section 5.3.1 "Timestamp Option" in RFC 3971. @@ -1641,14 +1641,14 @@ encodings that are currently supported are: ENC_TIME_TIMESPEC - 8 bytes; the first 4 bytes are seconds and the next 4 bytes are nanoseconds. - + ENC_TIME_TIMEVAL - 8 bytes; the first 4 bytes are seconds and the next 4 bytes are microseconds. - + ENC_TIME_SECS - 4 to 8 bytes, representing a value in seconds. - + ENC_TIME_MSECS - 6 to 8 bytes, representing a value in milliseconds. - + For other types, there is no support for proto_tree_add_item(). Now that definitions of fields have detailed information about bitfield |