[Rt-commit] [rtir] 01/02: Correct formatting of POD links

Thomas Sibley trs at bestpractical.com
Mon Jul 1 20:34:40 EDT 2013


This is an automated email from the git hooks/post-receive script.

trs pushed a commit to branch 2.9-trunk
in repository rtir.

commit 842a71048061de6bec9f9750b7d0499a93359e38
Author: Thomas Sibley <trs at bestpractical.com>
Date:   Mon Jul 1 17:31:49 2013 -0700

    Correct formatting of POD links
---
 docs/AdministrationTutorial.pod |  8 ++++----
 docs/DocIndex.pod               | 36 ++++++++++++++++++------------------
 docs/UPGRADING-3.0              |  2 +-
 etc/RTIR_Config.pm              |  2 +-
 4 files changed, 24 insertions(+), 24 deletions(-)

diff --git a/docs/AdministrationTutorial.pod b/docs/AdministrationTutorial.pod
index 291703b..dfc802f 100644
--- a/docs/AdministrationTutorial.pod
+++ b/docs/AdministrationTutorial.pod
@@ -89,7 +89,7 @@ IP addresses related to the incident, IR, investigation, or block.
 Don't rename this custom field or it will lose all associated features.
 It's possible to change this CF from multiple values to single value.
 
-See L<Tutorial/'IP'> for more information.
+See L<Tutorial/IP> for more information.
 
 See also L</SetIPFromContent> below.
 
@@ -275,10 +275,10 @@ It's OK to disable this scrip.
 
 Applies to the Incident Reports, Blocks, Incidents and Investigations queues.
 
-Uses the Constituency algorithms discussed in L<RT::IR::Constituencies> to
+Uses the Constituency algorithms discussed in F<docs/Constituencies.pod> to
 set and propagate changes to the Constituency custom field.  On ticket
 creation, Constituency is set based on the parent ticket, the
-X-RT-Mail-Extension header (see L<RT::IR::Constituencies>) or the default set
+X-RT-Mail-Extension header (see F<docs/Constituencies.pod>) or the default set
 in your F<RTIR_Config.pm>
 
 When linking tickets or changing the Constituency custom field, this
@@ -293,7 +293,7 @@ When tickets are created, or the Constituency custom field is updated,
 this scrip manages the assignment of DutyTeam groups as AdminCcs.
 It makes sure that for a Constituency EDUNET, a DutyTeam group
 named 'DutyTeam EDUNET' is assigned as AdminCc and removes other DutyTeam
-groups from the AdminCc.  L<RT::IR::Constituencies/ACLs> discusses
+groups from the AdminCc.  L<Constituencies/ACLs> discusses
 how to use these groups.
 
 =back
diff --git a/docs/DocIndex.pod b/docs/DocIndex.pod
index b3492af..51b3af4 100644
--- a/docs/DocIndex.pod
+++ b/docs/DocIndex.pod
@@ -22,7 +22,7 @@ See L<RT::Crypt::GnuPG> and L<AdministrationTutorial/GnuPG Encryption>
 
 =head3 Create new block via web-interface
 
-L<Tutorial/'Creating a Block'>
+L<Tutorial/Creating a Block>
 
 =head2 Managing Incident Responses
 
@@ -32,15 +32,15 @@ L<Tutorial/Merging Tickets>
 
 =head3 Split IR
 
-L<Tutorial/'Splitting tickets'>
+L<Tutorial/Splitting tickets>
 
 =head3 Reject IR
 
-L<Tutorial/'Rejecting an IR'>
+L<Tutorial/Rejecting an IR>
 
 =head3 Bulk Reject IR
 
-L<Tutorial/'Rejecting many IRs at once (bulk reject)'>
+L<Tutorial/Rejecting many IRs at once (bulk reject)>
 
 =head3 Linking IRs to Incidents
 
@@ -54,31 +54,31 @@ L<Tutorial/'Rejecting many IRs at once (bulk reject)'>
 
 =back
 
-L<Tutorial/'Linking IRs to Incidents'>
+L<Tutorial/Linking IRs to Incidents>
 
 =head2 Reply Reporters Incident
 
-L<Tutorial/'Reply to Reporters'>
+L<Tutorial/Reply to Reporters>
 
 =head2 Reply All Incident
 
-L<Tutorial/'Reply to All'>
+L<Tutorial/Reply to All>
 
 =head2 Link Incident with new IR
 
-L<Tutorial/'Linking Incidents to IRs, Investigations, etc.'>
+L<Tutorial/Linking Incidents to IRs, Investigations, etc.>
 
 =head2 Link Incident with existing IR
 
-L<Tutorial/'Linking Incidents to IRs, Investigations, etc.'>
+L<Tutorial/Linking Incidents to IRs, Investigations, etc.>
 
 =head2 Link Incident with new Block
 
-L<Tutorial/'Linking Incidents to IRs, Investigations, etc.'>
+L<Tutorial/Linking Incidents to IRs, Investigations, etc.>
 
 =head2 Link Incident with existing Block
 
-L<Tutorial/'Linking Incidents to IRs, Investigations, etc.'>
+L<Tutorial/Linking Incidents to IRs, Investigations, etc.>
 
 =head2 Resolve Incident
 
@@ -90,23 +90,23 @@ L<Tutorial/Resolving an Incident>
 
 =head2 Quick resolve Incident
 
-L<Tutorial/'Quick Resolve'>
+L<Tutorial/Quick Resolve>
 
 =head2 Abandon Incident
 
-L<Tutorial/'Abandoning Incidents'>
+L<Tutorial/Abandoning Incidents>
 
 =head3 Bulk Abandon Incidents
 
-L<Tutorial/'Abandoning Incidents', subsection 'Abandoning many Incidents at once (bulk abandon)'>
+L<Tutorial/Abandoning Many Incidents at Once (Bulk Abandon)>
 
 =head2 Launch Investigation
 
-L<Tutorial/'Linking Incidents to IRs, Investigations, etc.'>
+L<Tutorial/Linking Incidents to IRs, Investigations, etc.>
 
 =head2 Correspond with Correspondent
 
-L<Tutorial/'Correspond with Correspondent'>
+L<Tutorial/Correspond with Correspondent>
 
 =head2 Remove Blocks
 
@@ -118,11 +118,11 @@ L<Tutorial/Blocks>
 
 =head2 Split Blocks, Split Investigation, Split Incident
 
-L<Tutorial/'Merging Tickets'>
+L<Tutorial/Merging Tickets>
 
 =head2 Merge Blocks, Split Investigation, Split Incident
 
-L<Tutorial/'Merging Tickets'>
+L<Tutorial/Merging Tickets>
 
 =head2 These Actions are part of normal Ticket management in RT
 
diff --git a/docs/UPGRADING-3.0 b/docs/UPGRADING-3.0
index 9b100aa..dfb4592 100644
--- a/docs/UPGRADING-3.0
+++ b/docs/UPGRADING-3.0
@@ -107,7 +107,7 @@ In RTIR 3.0 we delete this basic implementation in favor of
 the extension. The SLA custom field stays as the extension uses it as
 well. However, the dependency on the extension is not mandatory and there
 is no default config for it. Read the tutorial for administrators for
-more info L<AdministrationTutorial/"Service Level Agreements (SLA)">.
+more info L<AdministrationTutorial/Service Level Agreements (SLA)>.
 
 The following scrip actions and scrips that use them are deleted:
 
diff --git a/etc/RTIR_Config.pm b/etc/RTIR_Config.pm
index c80a4be..cf6dd90 100644
--- a/etc/RTIR_Config.pm
+++ b/etc/RTIR_Config.pm
@@ -536,7 +536,7 @@ Set constituency propagation algorithm. Valid values are 'no',
 
 Read more about constituencies in F<lib/RT/IR/Constituencies.pod>.
 Algorithms are described in
-L<Constituencies/"Constituency Propagation Options">.
+L<Constituencies/Constituency Propagation Options>.
 
 =cut
 

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.


More information about the Rt-commit mailing list