osmocom
/
wireshark
11
0
Fork 1
Code Issues Pull Requests Projects Releases Wiki Activity

WSDG: Miscellaneous fixups. 

Change occurrences of GIT to Git. Fix a couple of URLs. Other changes.

Change-Id: I9eb69ee16f692c2bf71b62e7a2db4b762d9ab4bf
Reviewed-on: https://code.wireshark.org/review/29237
Petri-Dish: Gerald Combs <gerald@wireshark.org>
Tested-by: Petri Dish Buildbot
Reviewed-by: Anders Broman <a.broman58@gmail.com>
This commit is contained in:
Gerald Combs 2018-08-21 16:37:52 -07:00 committed by Anders Broman
parent a6a915abcc
commit ca355b8905
3 changed files with 19 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docbook/attributes.asciidoc
View File

@ -25,7 +25,7 @@
// Wireshark secondary URLs (pages)
:wireshark-authors-url: {wireshark-main-url}about.html#authors
:wireshark-buildbot-url: https://buildbot.wireshark.org/trunk/waterfall
:wireshark-buildbot-url: https://buildbot.wireshark.org/wireshark-master/waterfall
:wireshark-code-browse-url: {wireshark-code-review-url}/gitweb?p=wireshark.git
:wireshark-developers-guide-url: {wireshark-main-url}docs/
:wireshark-display-filter-reference-url: {wireshark-main-url}docs/dfref/

30
docbook/wsdg_src/WSDG_chapter_env_intro.asciidoc
View File

@ -240,7 +240,7 @@ files) these days.
You should use the released sources if you want to build Wireshark from
source on your platform for productive use. However, if you going to
develop changes to the Wireshark sources, it might be better to use the
latest GIT sources. For details about the different ways to get the
latest Git sources. For details about the different ways to get the
Wireshark source code see <<ChSrcObtain>>.
Before building Wireshark from a source distribution, make sure you have
@ -391,6 +391,17 @@ APIs available to the dissector developer, etc.
* The different mailing lists. See <<ChIntroMailingLists>>
[[ChIntroQA]]
==== Q&amp;A Site
The Wireshark Q&amp;A site at {wireshark-qa-url} offers a resource where
questions and answers come together. You have the option to search what
questions were asked before and what answers were given by people who
knew about the issue. Answers are graded, so you can pick out the best
ones easily. If your issue isn't discussed before you can post one
yourself.
[[ChIntroMailingLists]]
==== Mailing Lists
@ -414,10 +425,10 @@ If you want to be notified about all the changes to the bug
database, join this list. Details about the bug database can be
found in <<ChIntroBugDatabase>>.
wireshark-commits:: This list is for Wireshark developers. Every time a change to the GIT
wireshark-commits:: This list is for Wireshark developers. Every time a change to the Git
repository is checked in, a mail to this mailing list is generated.
If you want to be notified about all the changes to the GIT
repository, join this list. Details about the GIT repository can be
If you want to be notified about all the changes to the Git
repository, join this list. Details about the Git repository can be
found in <<ChSrcGitRepository>>.
You can subscribe to each of these lists from the Wireshark web site:
@ -443,17 +454,6 @@ The Wireshark community collects bug reports in a Bugzilla database at
reports, usually after some discussion on wireshark-dev, and automatic
bug reports from the Buildbot tools.
[[ChIntroQA]]
==== Q&amp;A Site
The Wireshark Q&amp;A site at {wireshark-qa-url} offers a resource where
questions and answers come together. You have the option to search what
questions were asked before and what answers were given by people who
knew about the issue. Answers are graded, so you can pick out the best
ones easily. If your issue isn't discussed before you can post one
yourself.
[[ChIntroReportProblems]]
==== Reporting Problems

6
docbook/wsdg_src/WSDG_chapter_sources.asciidoc
View File

@ -413,7 +413,7 @@ After the build process has successfully finished, you should find a
[TIP]
.Tip!
.Beware of multiple Wiresharks
====
An already installed Wireshark may interfere with your newly generated
version in various ways. If you have any problems getting your Wireshark
@ -466,7 +466,7 @@ launching the Wireshark.exe executable.
==== Unix/Linux
You can debug using command-line debuggers such as gdb, dbx, or lldb.
You can debug using command-line debuggers such as gdb, dbx, or lldb.
If you prefer a graphic debugger, you can use the Data Display Debugger
(ddd).
@ -478,7 +478,7 @@ Additional traps can be set on GLib by setting the `G_DEBUG` environment variabl
$ G_DEBUG=fatal_criticals ddd wireshark
----
See http://library.gnome.org/devel/glib/stable/glib-running.html[]
See https://developer.gnome.org/glib/stable/glib-running.html[]
[[ChSrcWin32Debug]]