[Freeciv-Dev] (PR#13397) Fix packets.def comment

["Per I. Mathisen" <per@xxxxxxxxxxx>]

<URL: http://bugs.freeciv.org/Ticket/Display.html?id=13397 >

Two field flags are listed as packet flags in the documentation. Attached
patch fixes this.

  - Per

Index: common/packets.def
===================================================================
RCS file: /home/freeciv/CVS/freeciv/common/packets.def,v
retrieving revision 1.138
diff -u -r1.138 packets.def
--- common/packets.def  27 Jun 2005 14:30:18 -0000      1.138
+++ common/packets.def  2 Jul 2005 20:32:56 -0000
@@ -90,18 +90,6 @@
      function is the player. handle-per-conn changes this to the
      connection the packet came from.
 
-     add-cap: only transfer this field if the given capability is
-     available at runtime. If you have a capability named
-     "new_version" a field line may look like this:
-       COORD x; add-cap(new_version)
-     when making an optional capability manditory, go through and remove
-     the add-cap flag for it while leaving the field intact.
-
-     remove-cap: don't transfer this field if the given capability is
-     available at runtime.  When making an optional capability manditory,
-     go through and remove entirely any fields marked as remove-cap with
-     that capability.
-
      dsend: request the creation of a dsend_packet_* function.  This is
      similar to a send function but instead of taking a packet struct
      as a parameter, it takes the fields of the packet as parameters.
@@ -145,6 +133,18 @@
 
       diff: use the array-diff feature. This will reduce the amount of
       traffic for large arrays in which only a few elements change.
+
+      add-cap: only transfer this field if the given capability is
+      available at runtime. If you have a capability named
+      "new_version" a field line may look like this:
+        COORD x; add-cap(new_version)
+      when making an optional capability manditory, go through and remove
+      the add-cap flag for it while leaving the field intact.
+
+      remove-cap: don't transfer this field if the given capability is
+      available at runtime.  When making an optional capability manditory,
+      go through and remove entirely any fields marked as remove-cap with
+      that capability.
 */
 
 # typedefs for numbers