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>
9 years ago · b6a9b8494c
parent d219887b44
commit b6a9b8494c
23 changed files with 0 additions and 54 deletions
--- a/doc/Makefile.am
+++ b/doc/Makefile.am
@ -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
--- a/doc/Makefile.nmake
+++ b/doc/Makefile.nmake
@ -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
--- a/doc/README.capture
+++ b/doc/README.capture
@ -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 
--- a/doc/README.design
+++ b/doc/README.design
@ -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
--- a/doc/README.developer
+++ b/doc/README.developer
@ -1,6 +1,3 @@
-$Revision$
-$Date$
-$Author$
 Tabsize: 4

 This file is a HOWTO for Wireshark developers. It describes general development
--- a/doc/README.dissector
+++ b/doc/README.dissector
@ -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
--- a/doc/README.epan_child
+++ b/doc/README.epan_child
@ -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.
--- a/doc/README.heuristic
+++ b/doc/README.heuristic
@ -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.

--- a/doc/README.idl2wrs
+++ b/doc/README.idl2wrs
@ -1,5 +1,3 @@
-$Id$
-
 Copyright (C) 2001 Frank Singleton <frank.singleton@ericsson.com>


--- a/doc/README.malloc
+++ b/doc/README.malloc
@ -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.
--- a/doc/README.packaging
+++ b/doc/README.packaging
@ -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$
--- a/doc/README.plugins
+++ b/doc/README.plugins
@ -1,5 +1,3 @@
-$Id$
-
 1. Plugins

 Writing a "plugin" dissector is not very different from writing a standard
--- a/doc/README.python
+++ b/doc/README.python
@ -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>
--- a/doc/README.regression
+++ b/doc/README.regression
@ -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.
--- a/doc/README.request_response_tracking
+++ b/doc/README.request_response_tracking
@ -1,5 +1,3 @@
-$Id$
-
 1. Introduction

 It is often useful to enhance dissectors for request/response style protocols
--- a/doc/README.stats_tree
+++ b/doc/README.stats_tree
@ -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
--- a/doc/README.tapping
+++ b/doc/README.tapping
@ -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
--- a/doc/README.wmem
+++ b/doc/README.wmem
@ -1,5 +1,3 @@
-$Id$
-
 1. Introduction

 The 'emem' memory manager (described in README.malloc) has been a part of
--- a/doc/README.xml-output
+++ b/doc/README.xml-output
@ -1,6 +1,5 @@
 Protocol Dissection in XML Format
 =================================
-$Id$
 Copyright (c) 2003 by Gilbert Ramirez <gram@alumni.rice.edu>


--- a/doc/dfilter2pod.pl
+++ b/doc/dfilter2pod.pl
@ -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
--- a/doc/eproto2sgml
+++ b/doc/eproto2sgml
@ -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>) {
--- a/doc/packet-PROTOABBREV.c
+++ b/doc/packet-PROTOABBREV.c
@ -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
--- a/doc/randpkt.txt
+++ b/doc/randpkt.txt
@ -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