Changeset 8558044 for general/prog/gitserver.xml

Timestamp:

09/06/2021 05:42:49 PM (3 years ago)

Author:

Pierre Labastie <pierre.labastie@…>

Branches:

11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

fef4473

Parents:

7999839

Message:

Remove spaces at the end of lines

I know it is somewhat useless, but I don't like them for
two reasons: first they cannot be seen, and I do not like things I
cannot see. Second, git highlights them, and this is disturbing...

File:

• general/prog/gitserver.xml (modified) (15 diffs)

general/prog/gitserver.xml

@@ -23 +23 @@
       This section will describe how to set up, administer and secure a
       <application>git</application> server. <application>Git</application>
-      has many options available. For more detailed documentation see 
-      <ulink url="https://git-scm.com/book/en/v2"/>. 
+      has many options available. For more detailed documentation see
+      <ulink url="https://git-scm.com/book/en/v2"/>.
     </para>
 
@@ -68 +68 @@
         Putting in an unuable password hash (replacing the <literal>!</literal>
         by <literal>NP</literal>) unlocks the account but it cannot be used
-        to login via password authentication. That is required by 
+        to login via password authentication. That is required by
         <application>sshd</application> to work properly.
         Next, create some files and directories in the home directory of the git user
         allowing access to the git repository using ssh keys.
       </para>
-      
+
 <screen role="root"><userinput>install -o git -g git -dm0700 /home/git/.ssh &amp;&amp;
 install -o git -g git -m0600 /dev/null /home/git/.ssh/authorized_keys</userinput></screen>
@@ -89 +89 @@
 
       <para>
-        It is also useful to set the default name of the initial branch 
+        It is also useful to set the default name of the initial branch
         of new repositories by modifying the git configuration. As the
         <systemitem class='username'>root</systemitem> user, run:
@@ -103 +103 @@
         can be executed:
       </para>
-      
+
 <screen role="root"><userinput>echo "/usr/bin/git-shell" &gt;&gt; /etc/shells</userinput></screen>
 
@@ -123 +123 @@
         <para>
           In all the instructions below, we use <emphasis>project1</emphasis>
-          as an example repository name.  You should name your repository 
+          as an example repository name.  You should name your repository
           as a short descriptive name for your specific project.
         </para>
@@ -132 +132 @@
 git init --bare                                      &amp;&amp;
 chown -R git:git .</userinput></screen>
-    
+
     </sect3>
 
@@ -171 +171 @@
       <note>
         <para>
-          The <emphasis>gitserver</emphasis> term used below 
-          should be the host name (or ip address) of the git server. 
+          The <emphasis>gitserver</emphasis> term used below
+          should be the host name (or ip address) of the git server.
         </para>
       </note>
@@ -188 +188 @@
 
       <para>The initial content is now pushed to the server and
-        is available for other users. On the current machine, the 
+        is available for other users. On the current machine, the
         argument <literal>--set-upstream origin trunk</literal> is
         now no longer required as the local repository is now
@@ -196 +196 @@
 
 <screen role="nodump"><userinput>git push</userinput></screen>
-      
+
       <para>
         Other developers can now clone the repository and do
@@ -230 +230 @@
 
       <para>
-        In the URL used to clone the project, the absolute path (here 
+        In the URL used to clone the project, the absolute path (here
         <filename>/srv/git/project1.git</filename>) has to be specified
         as the repository is not in git's home directory but in
@@ -252 +252 @@
         The setup described above makes a repository available for
         authenticated users (via providing the ssh public key file).
-        There is also a simple way to publish the 
+        There is also a simple way to publish the
         repository to unauthenticated users &mdash; of course without write
         access.
@@ -262 +262 @@
         daemon is in most cases enough for a development site.
       </para>
-      
+
       <note>
         <para>
@@ -344 +344 @@
             </para>
             <para>Specify the location of the git repositories.
-              Relative paths used when accessing the daemon will 
+              Relative paths used when accessing the daemon will
               translated relative to this directory.
             </para>
@@ -381 +381 @@
 
       <para>
-        As the base directory is <filename class="directory">/srv/git</filename> 
+        As the base directory is <filename class="directory">/srv/git</filename>
         by default (or set to a custom value in the configuration),
         <application>git</application> interprets the incoming path
@@ -388 +388 @@
         served.
       </para>
-      
+
     </sect3>