[PATCH (amend)] gitweb: 'pickaxe' and 'grep' features requires 'search' to be enabled

From

Jakub Narebski <jnareb@gmail.com>

Date

Jun 21, 2011, 06:41 UTC

Message-ID

<20110621064037.17169.36375.stgit@localhost.localdomain>

In-Reply-To

<20110620213904.11650.60345.stgit@localhost.localdomain>

Add a comment about this.

Signed-off-by: Jakub Narebski <jnareb@gmail.com>
---
I'm sorry, I forgot that this issue applies to 'grep' feature too.

 gitweb/gitweb.perl |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
index c9e6426..63af8d4 100755
--- a/gitweb/gitweb.perl
+++ b/gitweb/gitweb.perl
@@ -328,6 +328,7 @@ our %feature = (
 	# Enable grep search, which will list the files in currently selected
 	# tree containing the given string. Enabled by default. This can be
 	# potentially CPU-intensive, of course.
+	# Note that you need to have 'search' feature enabled too.
 
 	# To enable system wide have in $GITWEB_CONFIG
 	# $feature{'grep'}{'default'} = [1];
@@ -342,6 +343,7 @@ our %feature = (
 	# Enable the pickaxe search, which will list the commits that modified
 	# a given string in a file. This can be practical and quite faster
 	# alternative to 'blame', but still potentially CPU-intensive.
+	# Note that you need to have 'search' feature enabled too.
 
 	# To enable system wide have in $GITWEB_CONFIG
 	# $feature{'pickaxe'}{'default'} = [1];