git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 5/6] doc: fix indentation of listing blocks in gitweb.conf.txt

From
Andreas Heiduk <asheiduk@gmail.com>
Date
Oct 22, 2018, 20:45 UTC
Message-ID
<20181022204546.20354-6-asheiduk@gmail.com>
In-Reply-To
<20181022204546.20354-1-asheiduk@gmail.com>

'gitweb.conf.txt' uses inconsistent indentation in listing blocks and a mix of listing blocks and literal paragraphs. Both didn't look pretty in the rendered HTML page.

Signed-off-by: Andreas Heiduk <asheiduk@gmail.com>
---
 Documentation/gitweb.conf.txt | 25 +++++++++++++++----------
 1 file changed, 15 insertions(+), 10 deletions(-)
diff --git a/Documentation/gitweb.conf.txt b/Documentation/gitweb.conf.txt
index 9c8982ec98..c0a326e388 100644
--- a/Documentation/gitweb.conf.txt
+++ b/Documentation/gitweb.conf.txt
@@ -19,10 +19,12 @@ end of a line is ignored.  See *perlsyn*(1) for details.
 
 An example:
 
-    # gitweb configuration file for http://git.example.org
-    #
-    our $projectroot = "/srv/git"; # FHS recommendation
-    our $site_name = 'Example.org >> Repos';
+------------------------------------------------
+# gitweb configuration file for http://git.example.org
+#
+our $projectroot = "/srv/git"; # FHS recommendation
+our $site_name = 'Example.org >> Repos';
+------------------------------------------------
 
 
 The configuration file is used to override the default settings that
@@ -357,6 +359,7 @@ $home_link_str::
 +
 For example, the following setting produces a breadcrumb trail like
 "home / dev / projects / ..." where "projects" is the home link.
++
 ----------------------------------------------------------------------------
     our @extra_breadcrumbs = (
       [ 'home' => 'https://www.example.org/' ],
@@ -901,14 +904,16 @@ To enable blame, pickaxe search, and snapshot support (allowing "tar.gz" and
 "zip" snapshots), while allowing individual projects to turn them off, put
 the following in your GITWEB_CONFIG file:
 
-	$feature{'blame'}{'default'} = [1];
-	$feature{'blame'}{'override'} = 1;
+--------------------------------------------------------------------------------
+$feature{'blame'}{'default'} = [1];
+$feature{'blame'}{'override'} = 1;
 
-	$feature{'pickaxe'}{'default'} = [1];
-	$feature{'pickaxe'}{'override'} = 1;
+$feature{'pickaxe'}{'default'} = [1];
+$feature{'pickaxe'}{'override'} = 1;
 
-	$feature{'snapshot'}{'default'} = ['zip', 'tgz'];
-	$feature{'snapshot'}{'override'} = 1;
+$feature{'snapshot'}{'default'} = ['zip', 'tgz'];
+$feature{'snapshot'}{'override'} = 1;
+--------------------------------------------------------------------------------
 
 If you allow overriding for the snapshot feature, you can specify which
 snapshot formats are globally disabled. You can also add any command-line
-- 
2.19.1
Previous: Andreas HeidukNext: Andreas Heiduk
Message 6 of 8 in “various fixes for docs”
  1. 0/6 various fixes for docsAndreas Heiduk, Oct 22, 2018
  2. 1/6 doc: clarify boundaries of 'git worktree list --porcelain'Andreas Heiduk, Oct 22, 2018
  3. Eric SunshineOct 22, 2018
  4. 2/6 doc: fix ASCII art tab spacingAndreas Heiduk, Oct 22, 2018
  5. 3/6 doc: fix inappropriate monospace formattingAndreas Heiduk, Oct 22, 2018
  6. 5/6 doc: fix indentation of listing blocks in gitweb.conf.txtAndreas Heiduk, Oct 22, 2018
  7. 6/6 doc: fix formatting in git-update-refAndreas Heiduk, Oct 22, 2018
  8. 4/6 doc: fix descripion for 'git tag --format'Andreas Heiduk, Oct 22, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.