Git commit 70f44a9a2fd4d93bab5141ddca996b0f887bf7df by Burkhard L?ck.
Committed on 24/02/2013 at 12:53.
Pushed by lueck into branch 'master'.

fix links + replace sourceforge Patch Tracker with Review Board

M  +6    -5    doc/faq.docbook

http://commits.kde.org/krusader/70f44a9a2fd4d93bab5141ddca996b0f887bf7df

diff --git a/doc/faq.docbook b/doc/faq.docbook
index dc1f782..cc0b308 100644
--- a/doc/faq.docbook
+++ b/doc/faq.docbook
@@ -234,8 +234,8 @@
           <tip>
             <para>For more information about RPM, visit
             <ulink url="http://www.rpm.org/";>rpm.org</ulink> and read the
-            <ulink 
url="http://fedora.redhat.com/docs/drafts/rpm-guide-en/";>RPM Guide</ulink> by 
Eric
-            Foster-Johnson.</para>
+            <ulink 
url="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html";>RPM
 Guide</ulink> 
+            by Eric Foster-Johnson.</para>
           </tip>
           <para></para>
           <!-- Empty line to make it more readable -->
@@ -512,7 +512,8 @@
           you will probably be able to build a
           &krusader; RPM too. Information about RPM can
           be found at <ulink url="http://www.rpm.org/";>rpm.org</ulink> and in 
the
-          <ulink url="http://fedora.redhat.com/docs/drafts/rpm-guide-en/";>RPM 
Guide</ulink> by Eric Foster-Johnson. The
+          <ulink 
url="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html";>RPM
 Guide</ulink> 
+          by Eric Foster-Johnson. The
           following is the short procedure howto on building an
           RPM.</para>
           <warning>
@@ -1150,13 +1151,13 @@
               </para>
             </listitem>
             <listitem>
-             <para>Submit your patch files into our <ulink 
url="http://sourceforge.net/tracker/?group_id=6488&amp;atid=306488";>Patch 
Tracker</ulink>,
+             <para>Submit your patch files into the &krusader; group on the 
<ulink url="https://git.reviewboard.kde.org/groups/krusader/";>Review 
Board</ulink>,
               so that all patch proposals stay organised and do not get lost,
               tar.gz archives or diffs are usually ok.
               Do not copy changes into a mail. Most mailers will change the
               white spaces, so that the diff will not apply or the
               code snipped does not diff. In the past, patch mails went lost 
or disorganized in many many mails,
-              so please use the <ulink 
url="http://sourceforge.net/tracker/?group_id=6488&amp;atid=306488";>Patch 
Tracker</ulink>, thanks! 
+              so please use the <ulink 
url="https://git.reviewboard.kde.org/groups/krusader/";>Review Board</ulink>, 
thanks! 
               </para> 
             </listitem>
             <listitem>

Reply via email to