[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    developer.kde.org/documentation/other
From:       Dirk Mueller <mueller () kde ! org>
Date:       2005-05-08 19:55:55
Message-ID: 1115582155.573096.20643.nullmailer () svn ! kde ! org
[Download RAW message or body]

SVN commit 411283 by mueller:

fix email address



 M  +4 -4      trunk/developer.kde.org/documentation/other/developer-faq.html  


--- trunk/developer.kde.org/documentation/other/developer-faq.html #411282:411283
@@ -341,7 +341,7 @@
     to remove it.</p>
 
     <h3>Q: <a id="q1.8" name="q1.8">1.8. How do I get cvs access to kde?</a></h3>
-    <p>Send a mail to <a href="mailto:sysadmin (at) office (dot) kde (dot) \
org">sysadmin (at) office (dot) kde (dot) org</a> +    <p>Send a mail to <a \
href="mailto:sysadmin (at) kde (dot) org">sysadmin (at) kde (dot) org</a>  justify \
                why you need cvs access. Make sure to specify your full name
     and e-mail address, if the From field in your mails doesn't specify them. Please \
                include
     the name of your <a href="http://bugs.kde.org">bugs.kde.org</a> account if \
already existent @@ -491,7 +491,7 @@
     attempts to compromise KDE servers. Well known open source projects have been
     compromised this way in the past, <b>YOU</b> must help us to make sure that
     this doesn't happen with KDE servers as well. For that reason it is important to
-    notify sysadmin (at) office (dot) kde (dot) org immediately when you notice that \
someone may have +    notify sysadmin (at) kde (dot) org immediately when you notice \
                that someone may have
     had access to your private key for example when a computer on which it was
     stored has been hacked or infected with a virus, worm or trojan.
     </p>
@@ -504,7 +504,7 @@
     private/public key pair with <b>ssh-keygen -t dsa</b> .
     This will create a <b>private key</b> as <b>~/.ssh/id_dsa</b> and<br />
     a <b>public key</b> as <b>~/.ssh/id_dsa.pub</b>. In order to use SSH to access
-    KDE servers you need to send your <b>public key</b> to sysadmin (at) office \
(dot) kde (dot) org. +    KDE servers you need to send your <b>public key</b> to \
sysadmin (at) kde (dot) org.  </p>
 
     <h3>Q: <a id="q1.17" name="q1.17">1.17. My new CVS account aborts with \
<i>"commit" requires write @@ -1058,7 +1058,7 @@
 or
 cp foobar.cpp,v subdir/foobar.cpp,v</pre>
     <p>Note how <code>,v</code> was added to every file name.
-    Then send this list to <a href="mailto:sysadmin (at) office (dot) kde (dot) \
org">sysadmin (at) office (dot) kde (dot) org</a>. +    Then send this list to <a \
href="mailto:sysadmin (at) kde (dot) org">sysadmin (at) kde (dot) org</a>.  Once the \
files have been copied on the server, you can delete  the old ones from the client \
                using <code>cvs remove -f</code>
     and make the necessary changes (updating the Makefile.am in particular).</p>


[prev in list] [next in list] [prev in thread] [next in thread]