Age | Commit message (Collapse) | Author | Files | Lines |
|
Completion Diameter definition for mobileipv4.xml.
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4600
svn path=/trunk/; revision=32254
|
|
Diameter dictionary for MIPv4 is out of RFC4004.
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4587
svn path=/trunk/; revision=32213
|
|
svn path=/trunk/; revision=27300
|
|
svn path=/trunk/; revision=23559
|
|
svn path=/trunk/; revision=19889
|
|
svn path=/trunk/; revision=16551
|
|
svn path=/trunk/; revision=16498
|
|
the lines of what's done for RADIUS. That keeps them together (and
separate from other files), and makes the layout of the top-level source
directory closer to the layout of the installation directory, so that if
you run Ethereal or Tethereal from the top-level directory on Windows
it'll pick up the Diameter dictionary files (if it supports loading
them), and can do so on UN*X if we support a mechanism to let it find
its control files in the directory in which the binary resides.
Use the diameter_DATA, dtds_DATA, and radius_DATA macros in the
EXTRA_DIST macro, so you only have to change the lists of Diameter, DTD,
and RADIUS files in one place if you add or remove a file.
svn path=/trunk/; revision=16050
|