Remove $Id$ and other Subversion leftovers from the doc files.

Change-Id: I28a376f7e0fd90971f65ae9c1105a3ec85221470
Reviewed-on: https://code.wireshark.org/review/204
Reviewed-by: Jeff Morriss <jeff.morriss.ws@gmail.com>
This commit is contained in:
Jeff Morriss 2014-02-13 18:58:24 -05:00
parent d219887b44
commit b6a9b8494c
23 changed files with 0 additions and 54 deletions

View File

@ -1,8 +1,6 @@
# Makefile.am
# Automake file for Wireshark documentation
#
# $Id$
#
# Wireshark - Network traffic analyzer
# By Gerald Combs <gerald@wireshark.org>
# Copyright 1998 Gerald Combs

View File

@ -1,8 +1,6 @@
# Makefile.nmake
# Nmake file for Wireshark documentation
#
# $Id$
#
# Wireshark - Network traffic analyzer
# By Gerald Combs <gerald@wireshark.org>
# Copyright 1998 Gerald Combs

View File

@ -1,5 +1,3 @@
$Id$
This document is an attempt, to bring some light to the things done, when
packet capturing is performed. There might be things missing, and others
maybe wrong :-( The following will concentrate a bit on the win32 gtk

View File

@ -1,5 +1,3 @@
$Id$
Unfortunately, the closest thing to a design document is the
"README.developer" document in the "doc" directory of the Wireshark
source tree; however, although that's useful for people adding new

View File

@ -1,6 +1,3 @@
$Revision$
$Date$
$Author$
Tabsize: 4
This file is a HOWTO for Wireshark developers. It describes general development

View File

@ -1,6 +1,3 @@
$Revision$
$Date$
$Author$
Tabsize: 4
This file is a HOWTO for Wireshark developers interested in writing or working
@ -85,9 +82,6 @@ dissector should be changed to include that file.
You may not need to include all the headers listed in the skeleton, and you may
need to include additional headers.
The "$Id$" tag in the header comment will be updated by Subversion when the file
is checked in.
1.2 Explanation of needed substitutions in code skeleton.
In the skeleton sample code the following strings should be substituted with

View File

@ -1,7 +1,5 @@
EPAN CHILDREN
$ Id: $
This document is a work in progress.
This document describes a potential interface between a master process and one or more working children.

View File

@ -1,8 +1,3 @@
$Revision$
$Date$
$Author$
This file is a HOWTO for Wireshark developers. It describes how Wireshark
heuristic protocol dissectors work and how to write them.

View File

@ -1,5 +1,3 @@
$Id$
Copyright (C) 2001 Frank Singleton <frank.singleton@ericsson.com>

View File

@ -1,5 +1,3 @@
$Id$
IMPORTANT NOTE:
The emem interface (as described in this file) is deprecated.
Please use wmem (as described in README.wmem) for all new code.

View File

@ -109,5 +109,3 @@ case. E.g., "WireShark" is incorrect.
If you have a question not addressed here, send it to
wireshark-dev@wireshark.org.
$Id$

View File

@ -1,5 +1,3 @@
$Id$
1. Plugins
Writing a "plugin" dissector is not very different from writing a standard

View File

@ -9,8 +9,6 @@ FILE
DESCRIPTION
# wspy_dissector.py
#
# $Id$
#
# Wireshark Protocol Python Binding
#
# Copyright (c) 2009 by Sebastien Tandel <sebastien [AT] tandel [dot] be>

View File

@ -1,8 +1,6 @@
#
# Wireshark/TShark Regression Testing
#
# $Id$
#
# This is a sample Makefile for regression testing of the
# Wireshark engine. These tests use that uses 'tshark -V' to analyze all
# the frames of a capture file.

View File

@ -1,5 +1,3 @@
$Id$
1. Introduction
It is often useful to enhance dissectors for request/response style protocols

View File

@ -1,4 +1,3 @@
$Id$
tapping with stats_tree
Let's suppose that you want to write a tap only to keep counters, and you
@ -44,8 +43,6 @@ A small example of a very basic stats_tree plugin follows.
* A small example of stats_tree plugin that counts udp packets by termination
* 2005, Luis E. G. Ontanon
*
* $ ~Id: $
*
* Wireshark - Network traffic analyzer
* By Gerald Combs <gerald@wireshark.org>
* Copyright 1998 Gerald Combs

View File

@ -1,5 +1,3 @@
$Id$
The TAP system in Wireshark is a powerful and flexible mechanism to get event
driven notification on packets matching certain protocols and/or filters.
In order to use the tapping system, very little knowledge of Wireshark

View File

@ -1,5 +1,3 @@
$Id$
1. Introduction
The 'emem' memory manager (described in README.malloc) has been a part of

View File

@ -1,6 +1,5 @@
Protocol Dissection in XML Format
=================================
$Id$
Copyright (c) 2003 by Gilbert Ramirez <gram@alumni.rice.edu>

View File

@ -11,8 +11,6 @@
#
# Gilbert Ramirez <gram [AT] alumni.rice.edu>
#
# $Id$
#
# Wireshark - Network traffic analyzer
# By Gerald Combs <gerald@wireshark.org>
# Copyright 1998 Gerald Combs

View File

@ -7,8 +7,6 @@
# arg1 is the pod template file. The =insert_dfilter_table token
# will be replaced by the pod-formatted glossary
# STDOUT is the output
#
# $Id$
# Read all the data into memory
while (<STDIN>) {

View File

@ -2,8 +2,6 @@
* Routines for PROTONAME dissection
* Copyright 201x, YOUR_NAME <YOUR_EMAIL_ADDRESS>
*
* $Id$
*
* Wireshark - Network traffic analyzer
* By Gerald Combs <gerald@wireshark.org>
* Copyright 1998 Gerald Combs

View File

@ -1,7 +1,5 @@
Random Packet Generator
-----------------------
$Id$
randpkt is a small utility creates a libpcap trace file full of random packets.
You can control the number of packets, the maximum size of each packet,
and the type of each packet. It is not build by default, but you