From: Tyler Brazier <tyler@tylerbrazier.com>
Date: Fri, 2 Feb 2018 19:12:30 +0000 (-0600)
Subject: Remove SLOC comments
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=refs%2Fpull%2F45%2Fhead;p=i3%2Fi3.github.io

Remove SLOC comments

This change was made in the main repo but not for the docs
https://github.com/i3/i3status/commit/73620dc876d7f76b9a6771048c5ad0ade94e5bd7
---

diff --git a/_docs/i3status.man b/_docs/i3status.man
index 22d51ca..e9cc37d 100644
--- a/_docs/i3status.man
+++ b/_docs/i3status.man
@@ -24,13 +24,12 @@ configuration files in the following order:
 
 == DESCRIPTION
 
-i3status is a small program (about 1500 SLOC) for generating a status bar for
-i3bar, dzen2, xmobar, lemonbar or similar programs. It is designed to be very
-efficient by issuing a very small number of system calls, as one generally
-wants to update such a status line every second. This ensures that even under
-high load, your status bar is updated correctly. Also, it saves a bit of energy
-by not hogging your CPU as much as spawning the corresponding amount of shell
-commands would.
+i3status is a small program for generating a status bar for i3bar, dzen2,
+xmobar, lemonbar or similar programs. It is designed to be very efficient by
+issuing a very small number of system calls, as one generally wants to update
+such a status line every second. This ensures that even under high load, your
+status bar is updated correctly. Also, it saves a bit of energy by not hogging
+your CPU as much as spawning the corresponding amount of shell commands would.
 
 == CONFIGURATION
 
diff --git a/docs/i3status.html b/docs/i3status.html
index 4c1d257..568e79c 100644
--- a/docs/i3status.html
+++ b/docs/i3status.html
@@ -92,7 +92,7 @@ configuration files in the following order:
 <div class="sect1">
 <h2 id="_description">4. DESCRIPTION</h2>
 <div class="sectionbody">
-<div class="paragraph"><p>i3status is a small program (about 1500 SLOC) for generating a status bar for
+<div class="paragraph"><p>i3status is a small program for generating a status bar for
 i3bar, dzen2, xmobar or similar programs. It is designed to be very
 efficient by issuing a very small number of system calls, as one generally
 wants to update such a status line every second. This ensures that even under
diff --git a/i3status/index.html b/i3status/index.html
index a869269..424c800 100644
--- a/i3status/index.html
+++ b/i3status/index.html
@@ -7,13 +7,12 @@ title: i3status
 <h1>i3status</h1>
 
 <p>
-  i3status is a small program (about 3000 SLOC) for generating a status bar
-  for i3bar, dzen2, xmobar or similar programs. It is designed to be very
-  efficient by issuing a very small number of system calls, as one generally
-  wants to update such a status line every second. This ensures that even under
-  high load, your status bar is updated correctly. Also, it saves a bit of
-  energy by not hogging your CPU as much as spawning the corresponding amount
-  of shell commands would.
+  i3status is a small program for generating a status bar for i3bar, dzen2,
+  xmobar or similar programs. It is designed to be very efficient by issuing a
+  very small number of system calls, as one generally wants to update such a
+  status line every second. This ensures that even under high load, your status
+  bar is updated correctly. Also, it saves a bit of energy by not hogging your
+  CPU as much as spawning the corresponding amount of shell commands would.
 </p>
 
 <h2>Releases</h2>
diff --git a/i3status/manpage.html b/i3status/manpage.html
index 2d6ec32..88c009a 100644
--- a/i3status/manpage.html
+++ b/i3status/manpage.html
@@ -92,7 +92,7 @@ configuration files in the following order:
 <div class="sect1">
 <h2 id="_description">4. DESCRIPTION</h2>
 <div class="sectionbody">
-<div class="paragraph"><p>i3status is a small program (about 1500 SLOC) for generating a status bar for
+<div class="paragraph"><p>i3status is a small program for generating a status bar for
 i3bar, dzen2, xmobar, lemonbar or similar programs. It is designed to be very
 efficient by issuing a very small number of system calls, as one generally
 wants to update such a status line every second. This ensures that even under