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

[PATCH 3/7] gitweb: Improve comments about gitweb features configuration

From
Jakub Narebski <jnareb@gmail.com>
Date
Aug 26, 2006, 17:14 UTC
Message-ID
<11566124672096-git-send-email-jnareb@gmail.com>
In-Reply-To
<1156612392716-git-send-email-jnareb@gmail.com>
Signed-off-by: Jakub Narebski <jnareb@gmail.com>
---
 gitweb/gitweb.perl |   25 ++++++++++++++++---------
 1 files changed, 16 insertions(+), 9 deletions(-)
diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
index df2f9e5..c29ffa8 100755
--- a/gitweb/gitweb.perl
+++ b/gitweb/gitweb.perl
@@ -67,9 +67,16 @@ our $mimetypes_file = undef;
 # You define site-wide feature defaults here; override them with
 # $GITWEB_CONFIG as necessary.
 our %feature = (
-	# feature => {'sub' => feature-sub, 'override' => allow-override, 'default' => [ default options...]
-	# if feature is overridable, feature-sub will be called with default options;
-	# return value indicates if to enable specified feature
+	# feature => {
+	# 	'sub' => feature-sub (subroutine),
+	# 	'override' => allow-override (boolean),
+	# 	'default' => [ default options...] (array reference)}
+	#
+	# if feature is overridable (it means that allow-override has true value,
+	# then feature-sub will be called with default options as parameters;
+	# return value of feature-sub indicates if to enable specified feature
+	#
+	# use gitweb_check_feature(<feature>) to check if <feature> is enabled
 
 	'blame' => {
 		'sub' => \&feature_blame,
@@ -95,9 +102,9 @@ sub gitweb_check_feature {
 }
 
 # To enable system wide have in $GITWEB_CONFIG
-# $feature{'blame'}{'default'} =  [1];
-# To have project specific config enable override in  $GITWEB_CONFIG
-# $feature{'blame'}{'override'} =  1;
+# $feature{'blame'}{'default'} = [1];
+# To have project specific config enable override in $GITWEB_CONFIG
+# $feature{'blame'}{'override'} = 1;
 # and in project config gitweb.blame = 0|1;
 
 sub feature_blame {
@@ -113,9 +120,9 @@ sub feature_blame {
 }
 
 # To disable system wide have in $GITWEB_CONFIG
-# $feature{'snapshot'}{'default'} =  [undef];
-# To have project specific config enable override in  $GITWEB_CONFIG
-# $feature{'blame'}{'override'} =  1;
+# $feature{'snapshot'}{'default'} = [undef];
+# To have project specific config enable override in $GITWEB_CONFIG
+# $feature{'blame'}{'override'} = 1;
 # and in project config  gitweb.snapshot = none|gzip|bzip2
 
 sub feature_snapshot {
-- 
1.4.1.1
Previous: Jakub NarebskiNext: Jakub Narebski
Message 4 of 11 in “gitweb: Cleanups, fixes and small improvements”
  1. 0/7 gitweb: Cleanups, fixes and small improvementsJakub Narebski, Aug 26, 2006
  2. 1/7 gitweb: Restore old git_blame using git-annotate under "annotate"Jakub Narebski, Aug 26, 2006
  3. 2/7 gitweb: Remove workaround for git-diff bug fixed in f82cd3cJakub Narebski, Aug 26, 2006
  4. 3/7 gitweb: Improve comments about gitweb features configurationJakub Narebski, Aug 26, 2006
  5. 4/7 gitweb: Fix typo in git_patchset_bodyJakub Narebski, Aug 26, 2006
  6. 5/7 gitweb: Use 'local $/ = undef;' before 'print <$fd>;'Jakub Narebski, Aug 26, 2006
  7. 6/7 gitweb: blobs defined by non-textual hash ids can be cachedJakub Narebski, Aug 26, 2006
  8. 7/7 gitweb: Always link to plain version of the blob in git_blob.Jakub Narebski, Aug 26, 2006
  9. Junio C HamanoAug 26, 2006
  10. Jakub NarebskiAug 26, 2006
  11. Jakub NarebskiAug 27, 2006

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.